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

OAuth 2.1 #38

Open
cjslep opened this issue Nov 7, 2020 · 1 comment
Open

OAuth 2.1 #38

cjslep opened this issue Nov 7, 2020 · 1 comment
Labels
feature request New request for novel functionality
Milestone

Comments

@cjslep
Copy link
Member

cjslep commented Nov 7, 2020

Ensure other parts of the oauth2 server library conform to the OAuth 2.1 spec, which is more of a compilation of best practices and learnings from OAuth2.

The major differences from OAuth 2.0 are listed below.

  • PKCE is required for all OAuth clients using the authorization code flow
  • Redirect URIs must be compared using exact string matching
  • The Implicit grant (response_type=token) is omitted from this specification
  • The Resource Owner Password Credentials grant is omitted from this specification
  • Bearer token usage omits the use of bearer tokens in the query string of URIs
  • Refresh tokens for public clients must either be sender-constrained or one-time use
@cjslep cjslep added the feature request New request for novel functionality label Nov 7, 2020
@cjslep cjslep added this to the v1.0.0 milestone Nov 7, 2020
@cjslep
Copy link
Member Author

cjslep commented Dec 15, 2020

Turning the above into a checklist:

  • PKCE is required for all OAuth clients using the authorization code flow (see: investigate PKCE use with oauth2 library #36)
  • Redirect URIs must be compared using exact string matching
  • The Implicit grant (response_type=token) is omitted from this specification
  • The Resource Owner Password Credentials grant is omitted from this specification
  • Bearer token usage omits the use of bearer tokens in the query string of URIs
  • Refresh tokens for public clients must either be sender-constrained or one-time use

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

No branches or pull requests

1 participant