ServerIdentity failed validation, downgrading to anonymous

Steven Ostrowski

unread,

Nov 18, 2003, 9:38:28 AM11/18/03

to

I'm getting this error when trying to run one of the application
deployed in my domain. I only have one domain, so the information in the
error message list about enabling trust between domains should not apply
here.

I get the error mentioned in the topic with BEA code BEA-090513

What other ways are there to fix this error?

Steven Ostrowski

unread,

Nov 18, 2003, 9:15:49 AM11/18/03

to

Here's a more complete stack trace from the server log:

####<Nov 18, 2003 10:12:10 AM EST> <Error> <Security> <ORLEX1090> <demoServer>
<ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-090513>
<ServerIdentity failed validation, downgrading to anonymous.>
####<Nov 18, 2003 10:12:10 AM EST> <Error> <Security> <ORLEX1090> <demoServer>
<ExecuteThread: '0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-090513>
<ServerIdentity failed validation, downgrading to anonymous.>
####<Nov 18, 2003 10:12:10 AM EST> <Warning> <RMI> <ORLEX1090> <demoServer> <ExecuteThread:
'0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080003> <RuntimeException
thrown by rmi server: weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:557)
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:453)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:347)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:764)
at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Peter

unread,

Nov 26, 2003, 10:19:59 AM11/26/03

to

"Steven Ostrowski" <logbot-...@dealraider.com> wrote in message
news:3fba3017$1...@newsgroups.bea.com...

Is one server calling another server in the domain? Check to make sure that
you have a credential defined
in your config.xml. It could be that you are getting different credentials
because your managed servers
are rebooting and one does not exist in config.xml.

It should look something like this.
<SecurityConfiguration
Credential="{3DES}BNXOwiUeh3s2JMjMDpL1bPtQPe8jTp2Fi4Nb4Nve9wHyfmCG6OPEsrv2ZX
8v9RsieNHK6iBfc3A+/NXFcZp8rrzrfv9y1Aw1"
Name="mydomain" RealmBootStrapVersion="1"/>

Steven Ostrowski

unread,

Nov 26, 2003, 10:19:23 AM11/26/03

to

I figured out what was causing this problem, but I'm not sure why it
causes the problem.

I had another server (with a different server name) running on a
reachable location in my LAN. However, my domain in no way made any
calls to this other server. Yet, when I stopped the other server, I no
longer go the Server Identity error on my domain.

This doesn't make sense to me, but that was what was causing the error.