You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Velmurugan Periasamy (JIRA)" <ji...@apache.org> on 2014/10/24 03:39:33 UTC

[jira] [Updated] (ARGUS-130) LDAP authentication fails when user does not have search privileges

     [ https://issues.apache.org/jira/browse/ARGUS-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Velmurugan Periasamy updated ARGUS-130:
---------------------------------------
    Description: 
*Steps to reproduce* 
1] setup argus policy admin authentication method as LDAP
2] sync the users using argus user sync
3] login as a user with no search privileges

*Expected behavior*
User should be allowed to login. 

*Actual behavior*
Login fails with a message "In order to perform this operation a successful bind must be completed on the connection". Currently there is no ability to specify a different admin user with search privileges to bind.


  was:
*Steps to reproduce* 
1] setup argus policy admin authentication method as LDAP
2] sync the users using argus user sync
2] login as a user with no search privileges

*Expected behavior*
User should be allowed to login. 

*Actual behavior*
Login fails with a message "In order to perform this operation a successful bind must be completed on the connection". Currently there is no ability to specify a different admin user with search privileges to bind.



> LDAP authentication fails when user does not have search privileges
> -------------------------------------------------------------------
>
>                 Key: ARGUS-130
>                 URL: https://issues.apache.org/jira/browse/ARGUS-130
>             Project: Argus
>          Issue Type: Bug
>            Reporter: Velmurugan Periasamy
>            Assignee: Velmurugan Periasamy
>
> *Steps to reproduce* 
> 1] setup argus policy admin authentication method as LDAP
> 2] sync the users using argus user sync
> 3] login as a user with no search privileges
> *Expected behavior*
> User should be allowed to login. 
> *Actual behavior*
> Login fails with a message "In order to perform this operation a successful bind must be completed on the connection". Currently there is no ability to specify a different admin user with search privileges to bind.



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