fix: Configuration information not passed to Authentication providers by name #2198
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
dansiegel
approved these changes
Mar 13, 2024
dansiegel
reviewed
Mar 13, 2024
|
@mergify backport release/stable/4.0 |
✅ Backports have been created
|
nickrandolph
added a commit
that referenced
this pull request
Mar 15, 2024
….0/pr-2198 fix: Configuration information not passed to Authentication providers by name (backport #2198)
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.
GitHub Issue (If applicable): closes #2193
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Where there are multiple configurations for a given type, or they're referenced by name, the configuration doesn't return valid information
What is the new behavior?
Configuration sections are correctly registered by name
PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):