Limited Visibility of Compatibility Security MBeans The Default Security Configuration in the CompatibilityRealm

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

All Compatibility security MBeans are marked excluded and therefore have limited visibility in the WebLogic Scripting Tool. For example, the following command lists the attributes of the DomainMBean, excluding Compatibility security attributes such as FileRealmMBean: java weblogic.WLST connect ls However, if you address a Compatibility MBean directly, you can access it as in the following command: java weblogic.WLST connect cmo.getFileRealms

14.3 The Default Security Configuration in the CompatibilityRealm

By default, the CompatibilityRealm is configured with a Realm Adapter Adjudication provider, a Realm Adapter Authentication provider, a WebLogic Authorization provider, a Realm Adapter Authorization provider, a WebLogic Credential Mapping provider, and a WebLogic Role Mapping provider. ■ In the CompatibilityRealm, the Realm Adapter Authentication provider is populated with users and groups from the 6.x security realm defined in the config.xml file. – If you used the File realm in your 6.x security configuration, you can manage the users and groups in the Realm Adapter Authentication provider following the steps in Define users and Define groups topics of the Compatibility security section of the Oracle WebLogic Server Administration Console Help. – If you are using an alternate security realm LDAP, Windows NT, RDBMS, or custom, you must use the administration tools provided by that realm to manage users and groups. For information about configuring a Realm Adapter Authentication provider, see Section 14.4, Configuring a Realm Adapter Authentication Provider. You can use implementations of the weblogic.security.acl.CertAuthenticator class in Compatibility Using Compatibility Security 14-3 security by configuring the Identity Assertion provider in the Realm Adapter Authentication provider. For more information, see Section 14.5, Configuring the Identity Assertion Provider in the Realm Adapter Authentication Provider.