Technical data

14 Managing Security
14-38 Administration Guide
6. Configure the Caching realm. For more information, see “Configuring the
Caching Realm.”
Note: When you use an custom security realm, you must configure and enable
the Caching realm; otherwise, the custom security realm will not work.
When configuring the Caching realm, select the Custom Security realm from the
pull-down menu for the Basic attribute on the General tab. The Basic attribute
defines the association between the Caching realm and the custom security
realm.
7. Go to the Security node.
8. Choose the Filerealm tab.
9. In the Caching Realm attribute, choose the name of the Caching Realm to be
used with the custom security realm. A list of configured Caching Realms
appears on the pull-down menu.
Note: When you use an custom security realm, you must configure and enable
the Caching realm; otherwise, the custom security realm will not work.
10. Reboot WebLogic Server.
For information about writing a custom security realm, see Writing a Custom Security
Realm.
Migrating Security Realms
WebLogic Server provides a management architecture for security realms. The
management architecture implemented through MBeans allows you to manage
security realms through the Administration Console. If you have a security realm from
a previous release of WebLogic Server, use the following information to migrate to the
new architecture:
n If you are using the Windows NT, UNIX, or LDAP security realms, use the
Convert weblogic.properties option in the Administration Console to convert the
security realm to the new architecture. Note that you can view Users, Groups,
and ACLs in a Windows NT, UNIX, or LDAP security realm in the
Administration Console. However, you still need to use the tools in the Windows
NT, UNIX, or LDAP environments to manage Users and Groups.