-
Notifications
You must be signed in to change notification settings - Fork 108
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
Removing thumbprint check from PKeyAuth challenge #1733
Merged
Merged
Conversation
This file contains 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
… into melissaahn/RemoveThumbprintPKeyAuth
fadidurah
approved these changes
May 22, 2023
Please double check the failing tests. |
rpdome
approved these changes
May 22, 2023
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.
Seems like it's probably caused by the order you pushed the branch. once you get the common in and have this pointed to dev... it's probably solved.
melissaahn
added a commit
to AzureAD/microsoft-authentication-library-common-for-android
that referenced
this pull request
May 25, 2023
### Summary In the PKeyAuth protocol, the non-interactive flow can send a [thumbprint-based certificate challenge](https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-pkap/31066cbf-2462-4cb6-b0b9-68af2f21a5d0). This thumbprint is meant to serve as a hint to the client side to cross-check the thumbprint of the current device certificate. While we have logic for this check, it currently isn't being used due to [this line always returning true](https://github.com/AzureAD/microsoft-authentication-library-common-for-android/blob/478f706bf412b3bcc754ec90152568cb23826670/common4j/src/main/com/microsoft/identity/common/java/challengehandlers/PKeyAuthChallenge.java#L148) (go into the isValidIssuer method to see why). Additionally, the thumbprint is (supposedly, based on me asking some folks) hashed with SHA-1, and we're currently working to remove most of our use of SHA-1. [The iOS team has already removed their thumbprint verification logic](AzureAD/microsoft-authentication-library-for-objc#871), so we're going to do the same. This PR removes the logic related to the PKeyAuth thumbprint. No additions are being made. ### Related PRs - Broker: AzureAD/ad-accounts-for-android#2290 - MSAL: AzureAD/microsoft-authentication-library-for-android#1828 - ADAL: AzureAD/azure-activedirectory-library-for-android#1733
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Please see the common PR for description: AzureAD/microsoft-authentication-library-common-for-android#2045