refactor: replace isAdmin implementation#41171
Merged
phil-davis merged 6 commits intomasterfrom Feb 1, 2024
Merged
Conversation
isAdmin implementation
IljaN
approved these changes
Jan 31, 2024
Contributor
|
Various unit tests failed.
|
Contributor
|
Acceptance tests are all passing now, so external behavior is the same as before - good. The unit test just needs some adjustment - I will have a look. |
jvillafanez
reviewed
Feb 1, 2024
jvillafanez
reviewed
Feb 1, 2024
phil-davis
approved these changes
Feb 1, 2024
|
Author
|
thanks for your help! @phil-davis @jvillafanez |
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
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.

Description
Replace the
isAdminimplementationRelated Issue
Motivation and Context
Currently, the
isAdminmethod is indirectly calling thegetUserIdGroupswhich - in case an LDAP connection is configured - would require to hit the LDAP server. For this particular check, getting the admin group and listing the members should be preferable and would not have the disadvantages related to an unstable LDAP connection (it was i.e. observed that under certain circumstances the metrics app got disabled in case the LDAP server could not be reached)How Has This Been Tested?
Issue with the metrics app was not reproducible when intentionally causing an LDAP
BindFailedExceptionTypes of changes
Checklist: