[ 
https://issues.apache.org/jira/browse/RANGER-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612422#comment-14612422
 ] 

Don Bosco Durai commented on RANGER-567:
----------------------------------------

[Copying email response from Loïc]
Hi,

For your first issue, as far as I know Ranger UserSync service combined with a 
LDAP, it seems that you can only pull one attribute from your LDAP to create 
your user, but that attribute can be cn, dn, or email as well : you can 
configure it through the property SYNC_LDAP_USER_NAME_ATTRIBUTE in Ambari web 
interface.

But yes, basically, this attribute will be the User name, its First name and 
its Last name, as this is the only information Ranger gather about the user 
from the LDAP.

I am not aware of the development of a more complete mapping from LDAP user 
attributes to Ranger user ones, but feel free to create a JIRA about it.

As I have not experienced your third issue I can't answer it, but I'm very 
interested in the discussion as I am using it myself.
Regards,


Loïc

> UserSync service with LDAP don't fetch all attributes of a user.
> ----------------------------------------------------------------
>
>                 Key: RANGER-567
>                 URL: https://issues.apache.org/jira/browse/RANGER-567
>             Project: Ranger
>          Issue Type: Bug
>            Reporter: Hanish Bansal
>
> UserSync service is configured as : SYNC_LDAP_USER_NAME_ATTRIBUTE=cn
> Ranger is accepting only "cn" value from LDAP, Not accepting uid, sn, and 
> email address.
> I have created a user into ldap which has 
> cn- Mike Hemmingway
> sn- Hemmingway
> uid- mike
> emailaddress- [email protected]
> Every organization contains atleast above 4 details of users which are not
> migrating correctly into Ranger. 
> When it's migrating on Ranger then it's showing-
> User Name- Mike Hemmingway
> First name- Mike Hemmingway
> Last name- Mike Hemmingway
> Email address- <blank>
> Expected Behavior : All user attributes should be imported properly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to