Whether to allow one user to register multiple ClientIDs?

[daisukenishino2]

Requirement

At the moment, I am thinking with one user and one ClientID. If you want to add a new client dynamically instead of statically config file, you will need to sign up for as a new user. However, accounts that can add SAML and OAuth2 data should be controlled by permissions.

• https://github.com/OpenTouryoProject/MultiPurposeAuthSite/blob/develop/root/programs/MultiPurposeAuthSiteCore/MultiPurposeAuthSiteCore/Controllers/ManageController.cs#L2259
• https://github.com/OpenTouryoProject/MultiPurposeAuthSite/blob/develop/root/programs/MultiPurposeAuthSiteCore/MultiPurposeAuthSiteCore/Controllers/AccountController.cs#L4172
• https://github.com/OpenTouryoProject/MultiPurposeAuthSite/blob/develop/root/programs/MultiPurposeAuthSiteCore/MultiPurposeAuthSiteCore/Controllers/AccountController.cs#L792

[daisukenishino2]

Conclusion

I suggest using the email alias feature. The specification that one-account have one-client_id allows for the omission of OAuth2's redirect_uri.