[
https://issues.apache.org/jira/browse/SHIRO-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Demers resolved SHIRO-278.
--------------------------------
Resolution: Fixed
Assignee: (was: Les Hazlewood)
Renamed and added a child class of "JndiLdapRealm" to keep compatibility.
https://github.com/apache/shiro/commit/f4df3818d432be86a8d3efbe11c3da16fd5faf29
> Rename JndiLdapRealm to DefaultLdapRealm
> ----------------------------------------
>
> Key: SHIRO-278
> URL: https://issues.apache.org/jira/browse/SHIRO-278
> Project: Shiro
> Issue Type: Improvement
> Components: Realms
> Affects Versions: 1.1.0
> Reporter: Les Hazlewood
> Fix For: 1.3.0
>
>
> the existing name 'JndiLdapRealm' (which should be our default widely-used
> implementation) was chosen because it uses the JNDI API as an LDAP API.
> End-users have explained that they overlooked the class because they thought
> it implied that they needed to be using JNDI (e.g. in an app server) in order
> to use it.
> Because of this confusion, the name should be changed to 'DefaultLdapRealm'
> to indicate it is our default/common implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
