RANGER-5753: LDAP/Active Directory authentication does not validate local Ranger account status - #1174
Open
vyommani wants to merge 1 commit into
Open
RANGER-5753: LDAP/Active Directory authentication does not validate local Ranger account status#1174vyommani wants to merge 1 commit into
vyommani wants to merge 1 commit into
Conversation
…ocal Ranger account status
vyommani
requested review from
dineshkumar-yadav,
mneethiraj and
pradeepagrawal8184
August 24, 2026 02:54
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
1 participant
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.
What changes were proposed in this pull request?
When Ranger Admin is configured for LDAP or Active Directory authentication
(
ranger.authentication.method=LDAPorACTIVE_DIRECTORY),RangerAuthenticationProviderdid not check the local Ranger account's status after a successful directory bind. This meant
a user's local account status could be out of sync with their actual ability to sign in when
directory-based authentication was used, unlike local/JDBC authentication, which already
respects account status via the
STATUScolumn read by the JDBC user-details query.This change adds a status check,
UserMgr#isUserDisabled, and calls it fromRangerAuthenticationProvider#authenticateright after each successful LDAP, LDAP-bind,AD-bind, AD, PAM, and UNIX authentication branch, before the method returns — so a disabled
local account is rejected consistently across all supported authentication methods.
How was this patch tested?
added new unit tests.