Hi Miriam,
We had the same problem here. Our LDAP authentication was working up to
version 5.5.12 but broke on anything above it. I finally got it fixed
and I'll show you what we had previously and what we have now.
WORKED WITH 5.5.12 AND BELOW:
<Realm className="org.apache.catalina.realm.JNDIRealm"
debug="99"
connectionName="uid=xxx,ou=users,dc=bc,dc=com"
connectionPassword="passwd"
connectionURL="ldap://ldap.bc.com";
roleBase=""
roleName="cn"
roleSearch="(uniqueMember={0})"
roleSubtree="true"
userPattern="uid={0},ou=users,dc=bc,dc=com"
userSearch="(uid={0})"
userSubtree="true"
/>
WORKS WITH LATEST TOMCAT:
<Realm className="org.apache.catalina.realm.JNDIRealm"
debug="99"
connectionName="uid=xxx,ou=users,dc=bc,dc=com"
connectionPassword="passwd"
connectionURL="ldap://ldap.bc.com";
roleBase="ou=roleBase,dc=bc,dc=com"
roleName="cn"
roleSearch="(uniqueMember={0})"
roleSubtree="true"
userBase="ou=Users,dc=bc,dc=com"
userSearch="(uid={0})"
/>
________________________________
From: Miriam Keating [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 05, 2006 10:03 AM
To: [email protected]
Subject: FW: Question
Importance: High
QUMAS is the only global compliance company offering a complete solution
to regulated industries. Recognized as the world leader in Enterprise
Compliance Management.
* Website: www.qumas.com <BLOCKED::http://www.qumas.com/>
* Address: Cleve Business Park, Monahan Road, Cork, Ireland
* Office: +353-21-491 5100 +177
* Fax: +353-21-432 0394
________________________________
From: Miriam Keating
Sent: 05 October 2006 17:02
To: '[email protected]'
Subject: FW: Question
Importance: High
QUMAS is the only global compliance company offering a complete solution
to regulated industries. Recognized as the world leader in Enterprise
Compliance Management.
* Website: www.qumas.com <BLOCKED::http://www.qumas.com/>
* Address: Cleve Business Park, Monahan Road, Cork, Ireland
* Office: +353-21-491 5100 +177
* Fax: +353-21-432 0394
________________________________
From: Miriam Keating
Sent: 05 October 2006 16:59
To: '[email protected]'
Subject: Question
Importance: High
To whom it may concern,
I am connecting to LDAP using Tomcat 5.5.12 and everything is fine.
However, when I change over to Tomcat 5.5.16, I can no longer connect to
LDAP because of a binding error. The error I see is included in this
email. The cause of my problem is due to a change made to the JNDIRealm
class, the getUserByPattern(). The change made ( I don't think) has not
been documented in the change log html. Two lines of code have been
removed from the above class and method. Basically, can you tell me why
the change was made and also can you tell me is there a complimentary
change I need to make to my code, to get the LDAP to work.
Any help you can give me would be really appreciated.
Regards
Miriam
QUMAS is the only global compliance company offering a complete solution
to regulated industries. Recognized as the world leader in Enterprise
Compliance Management.
* Website: www.qumas.com <BLOCKED::http://www.qumas.com/>
* Address: Cleve Business Park, Monahan Road, Cork, Ireland
* Office: +353-21-491 5100 +177
* Fax: +353-21-432 0394
