[
https://issues.apache.org/jira/browse/SHIRO-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080508#comment-17080508
]
Brian Demers commented on SHIRO-588:
------------------------------------
+1 for cleaning up the structure in 2.0
LDAP is tricky, it been a while since I've had to deal with LDAP and AD, but
this is what I remember (I could be wrong):
There are 1 or 2 common setups for AD, and the dif between them is how groups
are stored
For LDAP, the sky is the limit, and there multiple "standard" schema people
follow, which is likely why the current LDAP realm is limited.
The Sonatype Nexus LDAP realm was fairly complete and supported multiple
schemas:
https://github.com/sonatype/nexus-public/tree/nexus-2.x/components/nexus-ldap-common/src/main/java/org/sonatype/security/ldap
> DefaultLdapRealm should extend AbstractLdapRealm
> ------------------------------------------------
>
> Key: SHIRO-588
> URL: https://issues.apache.org/jira/browse/SHIRO-588
> Project: Shiro
> Issue Type: Improvement
> Reporter: Brian Demers
> Priority: Major
> Fix For: 2.0.0
>
>
> DefaultLdapRealm not extending AbstractLdapRealm is confusing. If there is a
> reason for it, we should add that do the javadoc.
> From:
> http://shiro-user.582556.n2.nabble.com/Confused-By-Class-Hierarchy-tc7581289.html
> Note: this might not be a breaking change, as the API looks simliar (but
> needs another look)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
