Ticket #3 (closed bug: fixed)
Active Directory (LDAP) authentication [SF Bug 1677143]
| Reported by: | kohlhaas | Owned by: | kohlhaas |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3.2 |
| Version: | 1.3.2-RC1 | Keywords: | |
| Cc: |
Description (last modified by kohlhaas) (diff)
Active Directory (LDAP) authentication Private: (?)
No
I tried to configure rapla with Active Directory (windows 2003):
<plugin connectionPassword="ad123" userSearch="(sAMAccountName={0})"
enabled="true" class="org.rapla.plugin.jndi.JNDIPlugin"
userCn="sAMAccountName" contextFactory="com.sun.jndi.ldap.LdapCtxFactory"
userMail="userPrincipalName" connectionURL="ldap://192.168.36.35:389"
connectionName="CN=PortalAccountResolver,CN=Users,DC=mydomain,DC=com"
userBase="CN=Users,DC=mydomain,DC=com"/>
This is the best setup I managed to create, because it recognizes the
password
but:
when the Active directory password is correct I get a popup :
"Object for id [org.rapla.entities.User_2] not found"
on next try: User_3, User_4 and so on. When incorrent a popup with:
"Login failed"
I tried rapla 1.3 and latest CVS 1.3.1 version with tomcat 5.5.
Any advice? Is it a bug in config or in Rapla?
Change History
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/rapla.jpg)