shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SHIRO-587) Can't Access Groups If userPrincipalName Doesn't Exist
Date Fri, 21 Oct 2016 14:54:58 GMT

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

Brian Demers updated SHIRO-587:
-------------------------------
    Fix Version/s: 1.4.0

> Can't Access Groups If userPrincipalName Doesn't Exist
> ------------------------------------------------------
>
>                 Key: SHIRO-587
>                 URL: https://issues.apache.org/jira/browse/SHIRO-587
>             Project: Shiro
>          Issue Type: Bug
>            Reporter: opticyclic
>            Priority: Blocker
>             Fix For: 1.3.3, 1.4.0
>
>
> Sometimes you need to use sAMAccountName instead of userPrincipalName in your search.
> However, this is hard-coded in a private method
> https://github.com/apache/shiro/blob/master/core/src/main/java/org/apache/shiro/realm/activedirectory/ActiveDirectoryRealm.java#L171
> See here for a similar question on stackoverflow
> http://stackoverflow.com/questions/24062383/shiro-ldap-authorization-config/34896329#34896329
> There is a similar bug in Spring Security
> https://github.com/spring-projects/spring-security/issues/2448
> Making the search query was configurable in the shiro.ini would be useful.
> Making the getRoleNamesForUser protected instead of private would make sub-classing easier.
> Or keep the method private but make a protected method that returns Object[] searchArguments.



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

Mime
View raw message