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

8.1 RDBMS Compatablitity JMS Security issue

0 views
Skip to first unread message

Wade Mebed

unread,
Sep 5, 2003, 9:44:57 PM9/5/03
to

Migrating from Weblogic 7 SP2 to Weblogic 8.1, we get the following exception.
We are using RDBMS compatablitiy realm. Can you shed any light on this?

<Sep 5, 2003 9:17:40 AM PDT> <Error> <Security> <BEA-090060> <The AccessDecision
class "weblogic.security.providers.realmadapter.AuthorizationProviderImpl" returned
an error: com.downeysavings.lending.common.security.rdbmsrealm.RDBMSException:
realm initialization failed, action 'mbean.getDatabasePassword', - with nested
exception:
[weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword].
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:510)
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.getAttribute(RemoteMBeanServerImpl.java:282)
at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:610)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:442)
at weblogic.management.configuration.RDBMSRealmMBean_Stub.getDatabasePassword(RDBMSRealmMBean_Stub.java:163)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:132)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1303)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:100)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getAcl(RDBMSRealm.java:288)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1230)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1314)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:359)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:558)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:697)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:314)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:165)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at weblogic.ejb20.internal.JMSConnectionPoller.getDestination(JMSConnectionPoller.java:652)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1752)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
com.downeysavings.lending.common.security.rdbmsrealm.RDBMSException: realm initialization
failed, action 'mbean.getDatabasePassword', - with nested exception:
[weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword]
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:142)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1303)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:100)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getAcl(RDBMSRealm.java:288)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1230)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1314)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:359)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:558)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:697)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:314)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:165)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at weblogic.ejb20.internal.JMSConnectionPoller.getDestination(JMSConnectionPoller.java:652)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1752)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Sep 5, 2003 9:17:40 AM PDT> <Error> <Security> <BEA-090060> <The AccessDecision
class "weblogic.security.providers.realmadapter.AuthorizationProviderImpl" returned
an error: com.downeysavings.lending.common.security.rdbmsrealm.RDBMSException:
realm initialization failed, action 'mbean.getDatabasePassword', - with nested
exception:
[weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword].
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:510)
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.getAttribute(RemoteMBeanServerImpl.java:282)
at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:610)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:442)
at weblogic.management.configuration.RDBMSRealmMBean_Stub.getDatabasePassword(RDBMSRealmMBean_Stub.java:163)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:132)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1303)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:100)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getAcl(RDBMSRealm.java:288)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1230)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1314)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:359)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:558)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:697)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:314)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:165)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at weblogic.ejb20.internal.JMSConnectionPoller.getDestination(JMSConnectionPoller.java:652)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1752)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
com.downeysavings.lending.common.security.rdbmsrealm.RDBMSException: realm initialization
failed, action 'mbean.getDatabasePassword', - with nested exception:
[weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword]
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:142)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1303)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:100)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getAcl(RDBMSRealm.java:288)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1230)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1314)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:359)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:558)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:697)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:314)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:165)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at weblogic.ejb20.internal.JMSConnectionPoller.getDestination(JMSConnectionPoller.java:652)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1752)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
<Sep 5, 2003 9:17:41 AM PDT> <Error> <Security> <BEA-090060> <The AccessDecision
class "weblogic.security.providers.realmadapter.AuthorizationProviderImpl" returned
an error: com.downeysavings.lending.common.security.rdbmsrealm.RDBMSException:
realm initialization failed, action 'mbean.getDatabasePassword', - with nested
exception:
[weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword].
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword
at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:510)
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.getAttribute(RemoteMBeanServerImpl.java:282)
at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:610)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:442)
at weblogic.management.configuration.RDBMSRealmMBean_Stub.getDatabasePassword(RDBMSRealmMBean_Stub.java:163)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:132)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1303)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:100)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getAcl(RDBMSRealm.java:288)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1230)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1314)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:359)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:558)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:697)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:314)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:165)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at weblogic.ejb20.internal.JMSConnectionPoller.getDestination(JMSConnectionPoller.java:652)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1752)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
--------------- nested within: ------------------
com.downeysavings.lending.common.security.rdbmsrealm.RDBMSException: realm initialization
failed, action 'mbean.getDatabasePassword', - with nested exception:
[weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: RDBMSRealmConfig Action: read, Target: DatabasePassword]
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate.<init>(RDBMSDelegate.java:142)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSDelegate$DFactory.newInstance(RDBMSDelegate.java:1303)
at weblogic.security.utils.Pool.getInstance(Pool.java:57)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getDelegate(RDBMSRealm.java:100)
at com.downeysavings.lending.common.security.rdbmsrealm.RDBMSRealm.getAcl(RDBMSRealm.java:288)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1230)
at weblogic.security.acl.CachingRealm.getAcl(CachingRealm.java:1314)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.isAccessAllowed(AuthorizationProviderImpl.java:359)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:558)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:697)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:349)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:314)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:165)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:196)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
at weblogic.jndi.internal.ServerNamingNode_811_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:338)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at weblogic.ejb20.internal.JMSConnectionPoller.getDestination(JMSConnectionPoller.java:652)
at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1752)
at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1076)
at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:962)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Peter

unread,
Sep 7, 2003, 8:11:00 PM9/7/03
to

"Wade Mebed" <wme...@downeysavings.com> wrote in message
news:3f593c19$1...@newsgroups.bea.com...

>
> Migrating from Weblogic 7 SP2 to Weblogic 8.1, we get the following
exception.
> We are using RDBMS compatablitiy realm. Can you shed any light on this?
>

The anonymous user is trying to access a mbean attribute that is encrypted.
In 8.1, that requires
admin role. I think this is a bug, the realm code should be invoked with an
elevated permissions - file a support case.


Kevin Wang

unread,
Sep 8, 2003, 12:44:36 AM9/8/03
to

Peter, I think it is a good point that accessing a mbean attribute that is encrypted
requires admin role. But in first place, why can the realm code be accessed by
anonymous instead of <WLS Kernel>? Is this a bug you mean?

Peter

unread,
Sep 9, 2003, 8:15:41 PM9/9/03
to

"Kevin Wang" <y...@your.domain> wrote in message
news:3f5c...@newsgroups.bea.com...

>
> Peter, I think it is a good point that accessing a mbean attribute that is
encrypted
> requires admin role. But in first place, why can the realm code be
accessed by
> anonymous instead of <WLS Kernel>? Is this a bug you mean?
>

The code has just worked like that. The bug is whether the wls code should
be changed to run with
kernel id or whether the rdms realm should have to be changed.


0 new messages