opticyclic created SHIRO-587:

             Summary: 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

Sometimes you need to use sAMAccountName instead of userPrincipalName in your 
However, this is hard-coded in a private method

See here for a similar question on stackoverflow

There is a similar bug in Spring Security

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[] 

This message was sent by Atlassian JIRA

Reply via email to