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

Support OIDC device flow #766

Open
DiamondJoseph opened this issue Nov 5, 2024 · 0 comments
Open

Support OIDC device flow #766

DiamondJoseph opened this issue Nov 5, 2024 · 0 comments

Comments

@DiamondJoseph
Copy link

DiamondJoseph commented Nov 5, 2024

I have an application that currently makes use of the oauth2 device flow as it is a command line client while awaiting development of a web front end.

I'd like to test that the device flow is implemented correctly, e.g. that when the authentication server times out the request it is handled gracefully, that requests waits until the authentication server reports that the user has confirmed their identity out of band.

From my understanding, this would involve (for these examples, issuerId=main)

  • An additional endpoint at http://localhost:8080/main/device
  • An additional entry to the .well_known dictionary: "device_authorization_endpoint": "http://localhost:8080/main/device/code",
  • The ability to configure the behaviour of the device endpoint: what it returns as "device_code, user_code, verification_uri, verification_uri_complete expires_in (lifetime in seconds for device_code and user_code), and polling interval"
  • The ability to configure behaviour of an example device flow: number of polls or polling intervals to wait before reporting success/failure, whether to expect a call at the device endpoint before reporting success/failure.
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