Uh oh!
There was an error while loading. Please reload this page.
Device Authorization Grant support - #763
Conversation
caspernpo
commented
Sep 28, 2022
Just wondering, is there any progress on this PR? |
Arifin-pixel
commented
Oct 12, 2022
tes h&h ArFN Deso |
davidngoshadow
commented
Nov 6, 2023
Is there any update about this PR ? |
maxrimmer
commented
Dec 15, 2023
Any news on this? |
TheNetStriker
commented
Sep 18, 2024
I've just tested this and it works. I only found a typo in the readme: authService.performTokenPollRequestRequest has to times Request at the end, it should be Any update when this will be implemented? |
abdulazizumarovich
commented
Mar 15, 2025
Nice work. |
Dunedubby
commented
Sep 5, 2025
@blundell is there anything we can do to help make this merge happen? |
blundell
commented
Sep 15, 2025
I could merge it, but I don't have the authority or admin to make a release sorry. I am not sure who has either |
rofferom
commented
Apr 21, 2026
Can @agologan or @iainmcgin do it ? |
Checklist
Motivation and Context
As described in issue #675, AppAuth-Android does not currently support authentication for Android devices that either lack a browser or have limited input capabilities to fully perform the traditional authentication flow. Adding support of the extension Device Authorization Grant as described in RFC 8628 would allow such devices to obtain tokens from the authorization server with the help of a secondary device with browser and common input capabilities.
Description
The implementation follows the Device Authorization Grant - RFC 8628 and exposes the following:
DeviceAuthorizationRequestwith its associatedDeviceAuthorizationResponseurn:ietf:params:oauth:grant-type:device_codein the TokenRequest BuilderAuthorizationServiceAuthStateto properly handle the new authorization statesAs of today, there is no proper way for the user to sign off from devices without a browser, as this would require the extension Token Revocation - RFC 7009 that I would gladly implement after this one.