OTN Home > Oracle WebLogic Server 12.2.1.4.0 Documentation > Administration Console Online Help > Configure the RDBMS security store

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Configure the RDBMS security store

Before you begin

Before you configure the RDBMS security store, you must complete the steps described in the following topics:


WebLogic Server provides the option of using an external RDBMS as a datastore for the following security providers:

The RDBMS security store is required to use SAML 2.0 services in two or more WebLogic Server instances in a domain, such as in a cluster.

To configure the RDBMS security store:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane, select Security Realms.
  3. On the Summary of Security Realms page, select the name of the realm (for example, myrealm).
  4. On the Settings for RealmName page select RDBMS Security Store.
  5. Ensure the following attributes are set. If they are not set as described in the following list, the domain could be configured incorrectly.

    Note:

    • Changing the settings of the RDBMS Security Store Enabled attribute, or the database settings specified here, could result in a domain that cannot be booted if the security providers are unable to access their security policy data. As a best practice, you should avoid modifying the preceding settings of the RDBMS security store once it has been created by the Configuration Wizard.
    • If the RDBMS Security Store Enabled attribute is enabled, any security provider that is identified in this help topic and that is created in the security realm will use the RDBMS security store only, and not the embedded LDAP server. WebLogic Server does not support the ability to override this behavior for any of those providers.
    • Enabling the RDBMS security store has no effect on any security provider that is not included among those identified in this help topic.
  6. In the section labeled Server Synchronization Configuration, specify the appropriate settings for JNDI and JMS so that the RDBMS security store can cache database information in memory correctly. If the RDBMS is running in more than one JVM -- for example, the domain has multiple servers, or other Oracle products are sharing the same RDBMS store with the new domain -- these caches must be synchronized to ensure the integrity of the security data.

    To configure server synchronization:

    1. Specify a JNDI user name and password. This can be any valid user in the security realm who has access to JNDI.
    2. Create a JMS topic. You may reuse an existing one, if desired. For information, see Configure topics.

    Caution: Failure to configure JMS actions in a multiserver domain in which the RDBMS security store is configured may result in a security vulnerability.

  7. Click Save.
  8. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

Result

The domain is now configured so that any of the security providers identified in this help topic that are created in the security realm will use the RDBMS security store.

After you finish

If the JMS topic with which the RDBMS security store is configured goes down, see Managing the RDBMS Security Store for important information about restoring it.


Back to Top