-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(auth): prefer fido2 for reauth fallback #17391
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
Draft
goutamadwant
wants to merge
4
commits into
googleapis:main
Choose a base branch
from
goutamadwant:fix-google-auth-reauth-pyu2f
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+560
−127
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
c688dd5
fix: replace pyu2f reauth fallback with fido2
goutamadwant 49a4163
fix: handle fido2 device access errors
goutamadwant fe4cf2c
Merge branch 'googleapis:main' into fix-google-auth-reauth-pyu2f
goutamadwant 9ce8d95
fix: keep pyu2f as legacy reauth fallback
goutamadwant File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When communicating with a security key,
Ctap1(device).authenticate(...)can raise anOSError(or platform-specific subclasses likePermissionErrororFileNotFoundError) if the user lacks sufficient permissions (e.g., missing udev rules on Linux) or if the device is disconnected. Adding anexcept OSErrorblock ensures these common communication issues are handled gracefully by writing to stderr and continuing to the next device, rather than crashing the application.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Handled this too. If one security key raises OSError while authenticating, the fallback now writes the error and tries the next detected device.
Added coverage for the bad-device then good-device case.