Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

insufficient_authorization vs custom errors #133

Open
evert opened this issue Dec 4, 2024 · 0 comments
Open

insufficient_authorization vs custom errors #133

evert opened this issue Dec 4, 2024 · 0 comments

Comments

@evert
Copy link

evert commented Dec 4, 2024

The spec mentions that implementers should define their own error codes for specific challenges, and Appendix B.2. Gives an example of using the `otp_required' error code.

However, the spec also defines insufficient_authorization as:

The presented authorization is insufficient, and the authorization server is requesting the client take additional steps to complete the authorization.

Asking the client to supply a OTP code feels like an 'additional step'. Am I misunderstanding insufficient_authorization?

I'm also curious about the scenario where a user might take one of several possible steps to fulfill a challenge. For example, after providing a username and password a dialog may be presented where the user can choose either 'sending a code via email', 'sending a code via sms' or providing a TOTP code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant