Skip to content

FEAT - Add initial implementation of device code flow#90

Open
da1910 wants to merge 13 commits intoColin-b:developfrom
da1910:feat/device-code-flow
Open

FEAT - Add initial implementation of device code flow#90
da1910 wants to merge 13 commits intoColin-b:developfrom
da1910:feat/device-code-flow

Conversation

@da1910
Copy link
Copy Markdown

@da1910 da1910 commented Oct 26, 2025

Closes #17

This PR adds support for the device code OAuth2 flow as seen in https://datatracker.ietf.org/doc/html/rfc8628

The basic flow is that a user makes a request to the device_code endpoint which returns a device code, a user code and a verification URL. The user then opens the verification URL in a device of their choice and enters the user code.

The client polls the token endpoint, and once the user has authenticated they will receive a token and optionally a refresh token.

It's a work in progress for initial review as I mean to add subclasses for Okta, EntraID and for Auth0, as well as tidying up the tests and adding a changelog entry.

@da1910
Copy link
Copy Markdown
Author

da1910 commented Dec 28, 2025

I've given this a test with Auth0, it seems to do as expected. I can also give it a try with Entra ID, I don't have access to an Okta instance to test against however.

@da1910 da1910 marked this pull request as ready for review December 28, 2025 16:11
@da1910
Copy link
Copy Markdown
Author

da1910 commented Feb 21, 2026

Tested with Entra ID as well, seems to be doing the right thing. I've added unit tests for both.

I have also added the option to provide your own callback when the request is received, for uses where the library is integrated into a web-app or similar.

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

Successfully merging this pull request may close these issues.

Support device flow

2 participants