[Identity] Update async cert credential algorithm #39761
Draft
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
|
API change check API changes are not detected in this pull request. |
pvaneck
force-pushed
the
identity-cert-update
branch
from
c282611 to
2fdf473
Compare
Signed-off-by: Paul Van Eck <[email protected]>
pvaneck
force-pushed
the
identity-cert-update
branch
from
2fdf473 to
65d5437
Compare
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.
Since Entra docs recommend using the PS256 algorithm with PSS padding for certificate authentication, let's switch the default to use that for async cert credentials where we still maintain the signing logic.
Tested both PEM and PFX certs with an Entra ID app registration was able to authenticate successfully with these changes.
Closes: #39442