[
https://issues.apache.org/jira/browse/RANGER-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371329#comment-15371329
]
Selvamohan Neethiraj commented on RANGER-842:
---------------------------------------------
[~yujie.li]
1. If you set the PAM authentication, it should authenticate via PAM
authentication first; However, to support the LOCAL users, the authentication
will continue to JDBCAuthentication if the PAM authentication fails.
For non-LOCAL users, the encrypted-password stored in the JDBC table is
random plain-text, which will never match.
2. If the build machine does not have pam-devel library, the ranger pom.xml
will avoid building the PAM based authentication executable. So, you will not
have PAM executables (pamCredValidator.uexe) under ./unixauthpam/target/ folder.
Hope this answers your questions,
> Allow PAM for authentication
> ----------------------------
>
> Key: RANGER-842
> URL: https://issues.apache.org/jira/browse/RANGER-842
> Project: Ranger
> Issue Type: Improvement
> Components: admin
> Affects Versions: 0.5.1, 0.6.0
> Reporter: Bolke de Bruin
> Assignee: Selvamohan Neethiraj
> Labels: authentication, security
> Fix For: 0.6.0
>
> Attachments:
> 0001-RANGER-842-This-patch-adds-PAM-auth-support-to-range.patch,
> 0002-RANGER-842-modified-to-create-a-separate-module-for-.patch,
> 0003-RANGER-842-Fixed-Apache-License-Header-and-Added-add.patch
>
>
> Ranger currently uses shadow based authentication if configured for unix
> authentication. This way of authenticating is somewhat outdated as any recent
> Linux system (and many of the BSDs) have PAM available. PAM allows multiple
> authentication sources and also does authorization.
> Ranger should be able to use PAM for authentication
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
