Re: lookupUserFromDN to Active Directory fails after 405 upgrade
Thomas Draier <[email protected]>
| Newsgroups | gmane.comp.cms.jahia.devel |
|---|---|
| Message-ID | <[email protected]> |
hi, this may be related to a referral server problem, as described in http://www.mail-archive.com/[email protected]/msg00235.html . a patch was provided at that time, but it think it's not in 4.0.5, only in the cvs head - you can try to add the parameter described by anton in the connectToPublicDir method . but the complete stack trace would be useful for a better understanding of the problem. thomas Le 24 janv. 05, à 14:40, Pascal a écrit : > Both in the administration and in the user rights panels for > containers, looking up users in Active Directory yields the following > errors. > > Lookup of Active Directory groups works and login to the site with an > Active Directory user is no problem. The new settings in > group-router-config.xml and router-config.xml appear to be configured > correctly, including the > <factory>com.sun.jndi.ldap.LdapCtxFactory</factory> setting to which > the problem seems related. > > usermanager.JahiaUserManagerLDAPProvider lookupUserFromDN - JNDI > warning > javax.naming.PartialResultException. Root exception is > javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: > LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data > 52e, v893 > <snip> > WARN usermanager.JahiaUserManagerLDAPProvider lookupUserFromDN - JNDI > warning > javax.naming.NoInitialContextException: Need to specify class name in > environment or system property, or as an applet parameter, or in an > application resource file: java.naming.factory.initial > at > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java: > 652) > > Any help is appreciated > pascal