Java.lang.SecurityException while using RDBMSRealm in 5.1

Question

Hi,
We are in the process of migrating our application from Weblogic 4.5.1
to Weblogic 5.1. When we try to set up RdbmsRealm as the delegate realm
for the server and start the server, we get the following exception:
java.lang.SecurityException: User "system" does not have Permission
"read" based on ACL "weblogic.workspace.system".
at weblogic.security.acl.Security.logAndThrow(Security.java:372)
at weblogic.security.acl.Security.checkPermission(Security.java:254)
at
weblogic.workspace.server.Workspace.checkPermission(Workspace.java:1169)
at weblogic.workspace.server.Workspace.checkRead(Workspace.java:1174)
at weblogic.workspace.server.Workspace.fetch(Workspace.java:208)
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:243)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,
Compiled Code)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled
Code)
at
weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
The database has aclentries that grant read, write and reserve
permissions on weblogic.workspace.system to everyone. It is not clear
why the server still complains that user 'system' does not have
permissions. Is 'system' user not a part of everyone group by default? (
We are using the same acls we were using with Weblogic 4.5.1 ). Does
'everyone' group have all the users in it by default? Or has it changed?
Any suggestions welcome.
Thanks and Regards
Suresh B

Answer 1

Either try setting weblogic.allow.read.weblogic.workspace=system
Or add the system user to the group 'everyone' in the database you use for
RDBMSRealm (Hmm, not sure if this will work or not.
If you are implementing a custom realm then you need to explicitly state
which members are in the 'everyone' group.
(I've recently had a similar problem . I actually chose a different
solution, by overriding the isMember(user) method in RDBMSGroup to always
return true if the group's name is 'everyone' - I had to override the method
anyway, for other reasons. If anyone as any input on why this is a really
bad idea please feel free to tell me)
terry
BSuresh <[email protected]> wrote in message
news:[email protected]...
Hi,
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
weblogic.allow.read.weblogic.workspace.system=everyone
weblogic.allow.write.weblogic.workspace.system=everyone
I tried having the above entries in the weblogic.properties file but theserver
complains that weblogic.workspace acl is defined both in the delegate andbackup
realm. And the result remains the same - java.lang.SecurityException.User
"system" does not have Permission "read" based on ACL
"weblogic.workspace.system".
Thanks
Suresh.B
KNK wrote:
Try setting the "read" and "write" permissions explicitly in
weblogic.properties file.
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
-- KNK --
A ten thousand miles journey begins with a single step. That single stephas
to be taken from where you are, worries are no solution to any problem.
"BSuresh" <[email protected]> wrote in message
news:[email protected]...
Hi,
We are in the process of migrating our application from Weblogic 4.5.1
to Weblogic 5.1. When we try to set up RdbmsRealm as the delegate
realm
for the server and start the server, we get the following exception:
java.lang.SecurityException: User "system" does not have Permission
"read" based on ACL "weblogic.workspace.system".
at weblogic.security.acl.Security.logAndThrow(Security.java:372)
at weblogic.security.acl.Security.checkPermission(Security.java:254)
at
weblogic.workspace.server.Workspace.checkPermission(Workspace.java:1169)
>>>
at weblogic.workspace.server.Workspace.checkRead(Workspace.java:1174)
at weblogic.workspace.server.Workspace.fetch(Workspace.java:208)
at
weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:243
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java,
Compiled Code)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at
weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled
Code)
at
weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
>>>
The database has aclentries that grant read, write and reserve
permissions on weblogic.workspace.system to everyone. It is not clear
why the server still complains that user 'system' does not have
permissions. Is 'system' user not a part of everyone group by default?(
We are using the same acls we were using with Weblogic 4.5.1 ). Does
'everyone' group have all the users in it by default? Or has itchanged?
>>>
Any suggestions welcome.
Thanks and Regards
Suresh B