Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

LDAP Startup Problems

10 views
Skip to first unread message

Joshua Bennett

unread,
Dec 24, 2001, 12:06:25 PM12/24/01
to

Hello,


I am working on setting up our WebLogic Server (6.0) and WebLogic CommerceServer
3.5 with a Netscape LDAP Server. I followed the example and verified with our
LDAP group the correct connection info. However when I try to start WLCS I get
an Invalid Credentials exception. I know I am connecting to the LDAP server because
if I put in bogus info I get an Invalid Object Exception.
Is there any more debug info I can get. I have tried adding DebugSecurityRealm=true
to ServerDebug element in config.xml but that doesn't seem to show me anything
else.

I have also attached the Exception at the bottom of this message.


Thanks

Joshua Bennett


<Dec 24, 2001 10:57:55 AM CST> <Emergency> <Server> <Unable to initialize the
se
rver: 'Fatal initialization exception
Throwable: weblogic.security.ldaprealm.LDAPException: could not get context -
wi
th nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credential
s]]]
weblogic.security.ldaprealm.LDAPException: could not get context - with nested
e
xception:
[java.lang.reflect.InvocationTargetException - with target exception:
[javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credential
s]]]
at weblogic.security.ldaprealm.LDAPDelegate.getContext(LDAPDelegate.java
:207)
at weblogic.security.ldaprealm.LDAPDelegate.lookup(LDAPDelegate.java:227
)
at weblogic.security.ldaprealm.LDAPDelegate.getUserAttrs(LDAPDelegate.ja
va:356)
at weblogic.security.ldaprealm.LDAPDelegate.userExists(LDAPDelegate.java
:384)
at weblogic.security.ldaprealm.LDAPRealm.getUser(LDAPRealm.java:57)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:806
)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:670)
at weblogic.security.acl.internal.FileRealm.getPrincipalFromAnyRealm(Fil
eRealm.java:1003)
at weblogic.security.acl.internal.FileRealm.ensureRequiredObjectsExist(F
ileRealm.java:952)
at weblogic.security.acl.internal.FileRealm.loadMembers(FileRealm.java:1
202)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:281)
at weblogic.security.SecurityService.initialize(SecurityService.java:123
)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
***************************************************************************
The WebLogic Server did not start up properly.
Exception raised: weblogic.security.ldaprealm.LDAPException: could not get conte
xt - with nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credential
s]]]
java.lang.reflect.InvocationTargetException: javax.naming.AuthenticationExceptio
n: [LDAP: error code 49 - Invalid Credentials]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2655)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2601)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2406)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2323)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:211)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.jav
a:79)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
68)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.jav
a:83)
at weblogic.security.ldaprealm.LDAPDelegate$DFactory.newInstance(LDAPDel
egate.java:743)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at weblogic.security.ldaprealm.LDAPDelegate.getContext(LDAPDelegate.java
:203)
at weblogic.security.ldaprealm.LDAPDelegate.lookup(LDAPDelegate.java:227
)
at weblogic.security.ldaprealm.LDAPDelegate.getUserAttrs(LDAPDelegate.ja
va:356)
at weblogic.security.ldaprealm.LDAPDelegate.userExists(LDAPDelegate.java
:384)
at weblogic.security.ldaprealm.LDAPRealm.getUser(LDAPRealm.java:57)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:806
)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:670)
at weblogic.security.acl.internal.FileRealm.getPrincipalFromAnyRealm(Fil
eRealm.java:1003)
at weblogic.security.acl.internal.FileRealm.ensureRequiredObjectsExist(F
ileRealm.java:952)
at weblogic.security.acl.internal.FileRealm.loadMembers(FileRealm.java:1
202)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:281)
at weblogic.security.SecurityService.initialize(SecurityService.java:123
)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.security.ldaprealm.LDAPException: could not get context - with nested
e
xception:
[java.lang.reflect.InvocationTargetException - with target exception:
[javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credential
s]]]
at weblogic.security.ldaprealm.LDAPDelegate.getContext(LDAPDelegate.java
:207)
at weblogic.security.ldaprealm.LDAPDelegate.lookup(LDAPDelegate.java:227
)
at weblogic.security.ldaprealm.LDAPDelegate.getUserAttrs(LDAPDelegate.ja
va:356)
at weblogic.security.ldaprealm.LDAPDelegate.userExists(LDAPDelegate.java
:384)
at weblogic.security.ldaprealm.LDAPRealm.getUser(LDAPRealm.java:57)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:806
)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:670)
at weblogic.security.acl.internal.FileRealm.getPrincipalFromAnyRealm(Fil
eRealm.java:1003)
at weblogic.security.acl.internal.FileRealm.ensureRequiredObjectsExist(F
ileRealm.java:952)
at weblogic.security.acl.internal.FileRealm.loadMembers(FileRealm.java:1
202)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:281)
at weblogic.security.SecurityService.initialize(SecurityService.java:123
)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
***************************************************************************

Sunnynani (Reply@ToNewsgroup.Only)

unread,
Dec 24, 2001, 12:36:42 PM12/24/01
to
DebugSecurityRealm will help you in debugging the realm once the realm is
setup properly but it fails at the startup itself.

From the exception message, it definitely indicates that the incorrect
password is specified to connect to the LDAP. Verify it again!!

"Joshua Bennett" <jben...@cme.com> wrote in message
news:3c276091$1...@newsgroups.bea.com...

Joshua Bennett

unread,
Dec 26, 2001, 10:00:18 AM12/26/01
to

Thanks,
Just to verify the password would be set via the UserPasswordAttribute field
in the LDAPRealm element, correct?
Also would I need the BEA system account defined in the LDAP server?

Josh

Sunnynani (Reply@ToNewsgroup.Only)

unread,
Dec 26, 2001, 3:48:15 PM12/26/01
to
Yes, the userPassword attribute is used while authentication.

The user "system" needs to be in the default realm i.e.,
filerealm.properties file.

-- SunnyNani

"Joshua Bennett" <jben...@cme.com> wrote in message

news:3c29e602$1...@newsgroups.bea.com...

0 new messages