[
https://issues.apache.org/jira/browse/RANGER-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyom Mani Tiwari resolved RANGER-5753.
--------------------------------------
Fix Version/s: 3.0.0
2.10
Resolution: Fixed
> LDAP/Active Directory authentication does not validate local Ranger account
> status
> ----------------------------------------------------------------------------------
>
> Key: RANGER-5753
> URL: https://issues.apache.org/jira/browse/RANGER-5753
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 2.8.0, 2.9.0
> Reporter: Vyom Mani Tiwari
> Assignee: Vyom Mani Tiwari
> Priority: Critical
> Fix For: 3.0.0, 2.10
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> When Ranger Admin is configured to authenticate against LDAP or Active
> Directory ({{{}ranger.authentication.method=LDAP{}}} or
> {{{}ACTIVE_DIRECTORY{}}}), {{RangerAuthenticationProvider}} does not check
> the status of the corresponding local Ranger account before completing
> sign-in. As a result, a user's local account status can end up out of sync
> with whether they're actually able to log in when directory-based
> authentication is used.
> This differs from Ranger's local/JDBC login path, which already treats a
> disabled local account as unable to sign in (via the {{STATUS}} column read
> by the JDBC user-details query).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
