Allow metadata url keyrollover #197
Merged
Conversation
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
pablothedude
force-pushed
the
feature/allow-metadata-url-keyrollover
branch
23 times, most recently
from
f378931 to
63bc617
Compare
parijke
approved these changes
Jun 9, 2025
This is needed in order to integrate an identity provider with the help of a metadata url when doing a request. So an automatic key rollover can take place and the IdP config is cached from the metadata url. The update of the config is done in the callout itself and is not a separate flow. This was done to prevent downtime because only one certificate is in the metadata endpoint of the Microsoft identity providers. #194
pablothedude
force-pushed
the
feature/allow-metadata-url-keyrollover
branch
from
63bc617 to
0d23474
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.
This is needed in order to integrate an identity provider with the help
of a metadata url when doing a request. So an automatic key rollover
can take place and the IdP config is cached from the metadata url.
The update of the config is done in the callout itself and is not a
separate flow. This was done to prevent downtime because only one
certificate is in the metadata endpoint of the Microsoft identity
providers.
#194