Add x5c Header when Acquiring PoP Tokens #568
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
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.
If an SPN uses an SNI certificate for authentication, the x5c header must be included in the request. Omitting this header will cause the authentication call to fail. However, if the credentials are not a certificate, no error occurs, and the process continues without issues.
Failing call:
Pipeline Run
Error:
AADSTS700027: The certificate with the identifier used to sign the client assertion is not registered on the application. [Reason: The key was not found.] Thumbprint of the key used by the client:
Successful Run with Fix Applied:
Pipeline Run