[release-11.5.10] LDAP Authentication: Fix URL to propagate username context as parameter #111845
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
grafana-delivery-bot
bot
added
type/bug
area/frontend
add to changelog
backport
jtroy
approved these changes
Sep 30, 2025
|
🚀 Your submission is now being built and packaged.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport 7055ba9 from #111723
What is this feature?
Ensures the URL parameter matches the input field for testing LDAP User Mapping.
Why do we need this feature?
Resolves bug where username was not properly passed to LDAP debug page.
Who is this feature for?
Users with LDAP authentication configured in Grafana Enterprise
Which issue(s) does this PR fix?:
Fixes #111721
Special notes for your reviewer:
Please check that: