Accessing 6.x Security from Compatibility Security

Using Compatibility Security 14-5

14.8 Accessing 6.x Security from Compatibility Security

Using Compatibility security assumes that you have an existing config.xml file with a security realm that defines users and groups and ACLs that protect the resources in your WebLogic domain. WebLogic Server 6.x security management tasks such as configuring a security realm or defining ACLs should not be required and therefore those management tasks are not described in this section. However, if you corrupt an existing 6.x security realm and have no choice but to restore it, the following 6.x security management tasks are described in the Compatibility Security topic of the Oracle WebLogic Server Administration Console Help: ■ Configure LDAP V1 security realms ■ Configure LDAP V2 security realms ■ Configure RDBMS security realms ■ Configure Windows NT security realms ■ Configure wlauth for UNIX security realms ■ Configure UNIX security realms ■ Configure Custom security realms ■ Configure Caching realms ■ Configure the File realm ■ Define ACLs ■ Define groups ■ Delete groups ■ Define users ■ Delete users ■ Change user passwords ■ Change the system password ■ Disable the Guest user Caution: Compatibility security provides backward compatibility only and should not be considered a long-term security solution. 14-6 Securing Oracle WebLogic Server 15 Security Configuration MBeans 15-1 15 Security Configuration MBeans This section describes MBeans used in configuring the WebLogic Security Framework. Each MBean attribute is marked either dynamic, meaning that the attribute value can be changed without requiring a server restart, or non-dynamic, meaning that if you change the attribute value, you need to restart the server for the change to take effect. Note also that if an edit is made to a non-dynamic attribute, no edits to dynamic attributes will take effect until after restart. This is to assure that a batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated. Any security MBeans not listed are completely non-dynamic create or destroy MBean, change any attribute. For more information about WebLogic Security MBeans, see: ■ Managing Security Realms with JMX in Developing Custom Management Utilities With JMX for Oracle WebLogic Server ■ Security MBeans in the Oracle WebLogic Server MBean Reference

15.1 SSLMBean