Fix navigation in LDAP components #3670
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
* Fix navigation between ldap config and groups As there is no easy way to access each component through an URL any longer, use callbacks to let the parent decide which component to render. * Remove unused config prop * Use jsx extension for ldap component * Fix error handling in ldap groups component - Do not try to render an object, as that doesn't work - Display no configuration message when server returns 400, as that only happens when LDAP is not correctly configured. That message is a bit more clear and less scary Fixes #3485 (cherry picked from commit 1fafbf1)
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.
Fixes #3485, backport from #3651
(cherry picked from commit 1fafbf1)