First off, I don't see how a servlet filter will help with a JUnit test case.
If he/she was using Cactus, maybe.... but this is an issue with the login
module.
Also, NTLM is not being used here. Neillane is using LDAP, not Windows. So
Samba shouldn't be required.
Neillane,
For starters
|
|
| options.put("java.naming.provider.url",
"ldap://192.168.1.2:389/,o=,dc=,dc=,dc=");
|
|
Is the trailing ",o=,dc=,dc=,dc=" required? I have never used that in my
naming URL, but then, I've never gone against an OpenLDAP server, just general
LDAP systems. I believe this should just be the system name, directing JNDI to
bind to the server. The options do the rest.
| options.put("java.naming.security.authentication", "simple");
|
| options.put("bindDN", "cn=bob");
|
| options.put("bindCredential", "pwd");
|
Your BindDN should be a fully-qualified DN. For example:
cn=bob,cn=Users,dc=mycompany,dc=com
| options.put("baseCtxDN", "");
|
I'm not sure, but it may help to put a baseDN for your search, rather than
blank. If it's for the entire organization, then just include the DC's. For
example:
| options.put("baseCtxDN","dc=mycompany,dc=com").
|
If all your users are in the Users container, then you should use that as your
base:
| options.put("baseCtxDN","cn=Users,dc=mycompany,dc=com").
| options.put("baseFilter", "(cn={0})");
|
Can you post your LDIF data as well?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3908047#3908047
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3908047
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user