Thanks Nathan, I have the same settings in the initialDirContextFactory bean. The 127.0.0.1 is probably 'remote' from the perspective of the LDAP server, I think is correct.
Here's what else I tried: I created a 1.9.4 generic application, trying to see if that works with LDAP. Funny thing is, 1.9 didn't work with MySQL OR PostgreSQL, let alone LDAP! Same error message: ""[myproject] WARN [btpool0-1] LoggerListener.onApplicationEvent(60) Authentication event AuthenticationFailureBadCredentialsEvent: daniel.g; details: [EMAIL PROTECTED]:RemoteIpAddress: 127.0.0.1; SessionId: sw0bku8q9w30; exception: Bad credentials" I even checked the LDAP packets. For the first login, the app was trying to use the login user as bind user instead of 'managerDN' and failed. Then it did a bind using the managerDN, which was successful. Any login after that just tried to bind using the login name and failed. So: my 2.0 authentication works with MySQL and PostgreSQL but not with LDAP, my 1.9.4 does not work period. Out of ideas at this point... Cheers Gempy melinate wrote: > > It looks to me like Acegi is trying to connect to the wrong server > [127.0.0.1]. Have you tried connecting to the server > "DC01.mycompany.corp" rather than "DC01"? > > Nathan > > ----- Original Message ----- > From: "gempy" <[EMAIL PROTECTED]> > To: [email protected] > Sent: Wednesday, October 17, 2007 3:25:25 PM (GMT-0800) > America/Los_Angeles > Subject: [appfuse-user] Getting LDAP Bad Credentials exception... > > > Hello > > I've been trying to get the Appfuse generated webapp to authenticate users > against our AD server. I read all related postings in this forum, seems > like > for all users the solution presented here works: > http://appfuse.org/display/APF/LDAP+Authentication > > Not for me however. I have been getting fewer and fewer exceptions since I > started but this last one stumps me: > "[myproject] WARN [btpool0-1] LoggerListener.onApplicationEvent(60) | > Authentication event AuthenticationFailureBadCredentialsEvent: daniel.g; > details: [EMAIL PROTECTED]: > RemoteIpAddress: 127.0.0.1; SessionId: sw0bku8q9w30; exception: Bad > credentials > I get this for any user/password I enter in the login screen. > > These are my settings, I have used them with an LDAP browser and they > work: > > <bean id="initialDirContextFactory" > class="org.acegisecurity.ldap.DefaultInitialDirContextFactory"> > <constructor-arg > value="ldap://DC01:389/ou=Internal_Users,DC=main,DC=mycompany,DC=corp"/> > <property name="managerDn" value="CN=bind > user,CN=Users,DC=main,DC=mycompany,DC=corp"/> > <property name="managerPassword" value="password" /> > </bean> > > The "ldapProvider" bean is unchanged from the example. > > I tried not using a "managerDN' but our server does not accept anonymous > user binding. > I'm using Spring MVC model. > > Any help would be appreciated. > > Thanks > > -- > View this message in context: > http://www.nabble.com/Getting-LDAP-Bad-Credentials-exception...-tf4643726s2369.html#a13264210 > Sent from the AppFuse - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Getting-LDAP-Bad-Credentials-exception...-tf4643726s2369.html#a13279282 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
