Weblogic 9.2 RDBMS Custom Security Realm

[Sid varma]

hello guys,


We are currently planning to upgrade our Application currently running on Weblogic 9.2 to weblogic 10.3.6
The plan is to move the application to the new platform(will be sharing weblogic with other applications), instead of upgrading the domain of the old weblogic. We are running into 2 problems here.

First one is We currently have a RDBMS Custom Realm which we are using in Weblogic 9.2 Server under Compatibility Security. What do you think is the best way to deal with the OLD security realm ? Since we are not upgrading the existing domain's config.xml, there is no way we can get compatibility security in 10.3.6 (Or is there a way ?)
Also the old 9.2 server environment only had a single application deployed, but the new 10.3.6 server environment will be a shared one. So we fear even if we some how use the same compatibility security to support the old RDBMS realms, it might cause issues. Any suggestions on this ?

Second problem is new Weblogic.jar in the version 10.3.6 has been updated by removing deprecated objects – our custom security realm is dependent on those objects/classes which were removed. So we found a workaround by adding the OLD weblogic 9.2's webloigic.jar to the classpath. That by no means should be a solution. What would Oracle suggest about this ? Few of the classes that were removed from 10.3.6 (our RDBMS security realm uses these classes/objects in the code) are,
weblogic.security.acl.User;
weblogic.utils.NestedRuntimeException;
weblogic.security.acl.FlatGroup;
weblogic.security.acl.AbstractListableRealm;
weblogic.security.acl.BasicRealm;
weblogic.security.acl.User

Is the workaround we found good enough ? What would be the right way to deal with this problem ?

Any help/comments will be helpful than you think !

Thanks !!

[MdFaisal Khan]

Did you upgrade to reach to WLS 9.2?
Do you have a default authenticator as well?
So long you have a default authenticator and the control flag of the rdbms authenticator is not set to required/requisite other applications will not be affected.

Why don't you get rid of your compatability realm? it would require only a few changes in config n file..

You can set up a new rdbdms authenticator following my article here

http://weblogic-wonders.com/weblogic/2010/03/11/configuring-sql-authenticator-with-weblogic-server/

Let me know if you face any issues

Thanks,
Faisal

[Sid varma]

Faisal,

Thanks for the response.

Yes we upgraded the Weblogic 8 to get to 9.2

Yes, we do have the default security realm. But the authentication is done by the custom realm via Java Class. So without the custom realm, there is no authentication happening.