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

For OAuth2 device flow, should we define a "device authorization" element? #953

Closed
mmccool opened this issue Aug 17, 2020 · 4 comments
Closed
Assignees
Labels
PR needed Security V1.1 should be resolved in v1.1

Comments

@mmccool
Copy link
Contributor

mmccool commented Aug 17, 2020

See editor's note in text about this.
Also, might want to use deviceAuthorization instead of device_authorization if we do do it, for consistency.

@farshidtz
Copy link
Member

This is a blocker for #929

@egekorkan egekorkan added the V1.1 should be resolved in v1.1 label Oct 26, 2021
@mmccool
Copy link
Contributor Author

mmccool commented Nov 29, 2021

Discussed in security call Nov 29, 2021:

  • Current text uses the value of "authorization" for the "device authorization" endpoint
  • Adding a "device{_a,A}uthorization endpoint would require some additional rules about how that must be used for device flows and authorization must not, which would need extra validation and testing
  • Consensus: leave the design as it is (use "authorization" for "device authorization" and delete the editor's note (requires PR).

@mmccool
Copy link
Contributor Author

mmccool commented Nov 29, 2021

@mmccool: make a PR to delete the ed note

@egekorkan
Copy link
Contributor

Call of 15.06: This is solved by using authorization

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR needed Security V1.1 should be resolved in v1.1
Projects
None yet
Development

No branches or pull requests

3 participants