Skip to content

Conversation

hickford
Copy link
Owner

@hickford hickford commented Oct 13, 2023

https://datatracker.ietf.org/doc/html/rfc8628#section-3.3.1

When "verification_uri_complete" is included in the authorization response, clients MAY present this URI in a non-textual manner using any method that results in the browser being opened with the URI, such as with QR (Quick Response) codes or NFC (Near Field Communication), to save the user from typing the URI.

For usability reasons, it is RECOMMENDED for clients to still display the textual verification URI ("verification_uri") for users who are not able to use such a shortcut. Clients MUST still display the "user_code", as the authorization server will require the user to confirm it to disambiguate devices or as remote phishing mitigation.

Requires qrencode to be installed

Assumes server populates verification_uri_complete -- GitLab does, GitHub does not.

@hickford hickford force-pushed the qr branch 3 times, most recently from 8a65dc1 to 27ff133 Compare October 13, 2023 11:27
@hickford
Copy link
Owner Author

hickford commented Oct 13, 2023

Example screenshot:

image

@hickford hickford changed the title QR code for device auth Show QR code for device auth Oct 13, 2023
@AdityaGarg8
Copy link

I think we can use qrencode.de, thus eliminating the need of installing another software.

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.

2 participants