Running Compatibility Security: Main Steps

14 Using Compatibility Security 14-1 14 Using Compatibility Security Compatibility security is the capability to run security configurations developed with WebLogic Server 6.x in this release of WebLogic Server. In Compatibility security, you manage 6.x security realms, users, groups, and ACLs, protect user accounts, and configure the Realm Adapter Auditing provider and optionally the Identity Assertion provider in the Realm Adapter Authentication provider. The following sections describe how to configure Compatibility security: ■ Section 14.1, Running Compatibility Security: Main Steps ■ Section 14.2, Limited Visibility of Compatibility Security MBeans ■ Section 14.3, The Default Security Configuration in the CompatibilityRealm ■ Section 14.4, Configuring a Realm Adapter Authentication Provider ■ Section 14.5, Configuring the Identity Assertion Provider in the Realm Adapter Authentication Provider ■ Section 14.6, Configuring a Realm Adapter Auditing Provider ■ Section 14.7, Protecting User Accounts in Compatibility Security ■ Section 14.8, Accessing 6.x Security from Compatibility Security

14.1 Running Compatibility Security: Main Steps

To set up Compatibility security: 1. Make a backup copy of your 6.x WebLogic domain including your config.xml file before using Compatibility security. 2. Add the following to the 6.x config.xml file if it does not exist, replacing the values with the actual names of your domain, security realm, and FileRealm: Security Name=mydomain Realm=mysecurity Realm Name=mysecurity FileRealm=myrealm FileRealm Name=myrealm Note: Compatibility security is deprecated in this release of WebLogic Server and will not be supported in future major releases. Oracle strongly recommends upgrading your WebLogic Server deployment to the security features in this release of WebLogic Server. You should only use Compatibility security pending such an upgrade. 14-2 Securing Oracle WebLogic Server 3. Install the current version of WebLogic Server in a new directory location. Do not overwrite your existing 6.x installation directory. For more information, see Oracle WebLogic Server Installation Guide. 4. Modify the start script for your 6.x server to point to the new WebLogic Server installation. Specifically, you need to modify: ■ The classpath to point to the weblogic.jar file in the new WebLogic Server installation. ■ The JAVA_HOME variable to point to the new WebLogic Server installation. 5. Use the start script for your 6.x server to boot the new version of WebLogic Server. To verify whether you are running Compatibility security correctly, open the new WebLogic Server Administration Console. If you are running Compatibility security, a Compatibility Security node is displayed on the left in the Domain Structure pane.

14.2 Limited Visibility of Compatibility Security MBeans