Skip navigation.

Securing WebLogic Server

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Customizing the Default Security Configuration

The following sections provide information about customizing the default security configuration and creating a new security realm:

For information about configuring security providers, see Configuring WebLogic Security Providers, and Configuring Authentication Providers.

For information about migrating security data to a new security realm, see Migrating Security Data.

 


Why Customize the Default Security Configuration?

To simplify the configuration and management of security, WebLogic Server provides a default security configuration. In the default security configuration, myrealm is set as the default (active) security realm, and the WebLogic Adjudication, Authentication, Identity Assertion, Authorization, Credential Mapping, Role Mapping, and CertPath providers are defined as the security providers.

Customize the default security configuration if you want to:

For information about configuring different types of security providers in a security realm, see see Configuring WebLogic Security Providers, and Configuring Authentication Providers.

The easiest way to customize the default security configuration is to add the security providers you want to the default security realm (myrealm). However, BEA recommends the following procedure to customize the default security configuration:

  1. Create an entirely new security realm.
  2. Configure security providers in the new realm.
  3. Migrate any security data, such as users and groups, from the existing default security realm to the new realm.
  4. Set the new security realm as the default security realm.

The remainder of this section explains describes the configuration decisions that need to be made when creating a new security realm and the main steps used to create a new security realm. Configuring a security realm is only one step in creating a new security configuration; you also need to configure security providers in that realm before in order for the security realm to be valid. For information about configuring different types of security providers in a security realm, see Configuring WebLogic Security Providers, and Configuring Authentication Providers.

 


Configuration Decisions When Creating a New Security Realm

Before creating a new security realm, you need to make decisions about how the WebLogic Security service will use security information defined in deployment descriptors (DDs), the method for securing URLs and EJBs, and how credential maps will be managed.

When creating a new security realm, consider the following:

Note: When creating a new security realm, at least one of the configured Authentication providers must return asserted LoginModules. Otherwise, run-as tags defined in deployment descriptors will not work.

For more information, see Configure new security realms in the Administration Console online help.

 


Creating a New Security Realm: Main Steps

To create a new security realm:

  1. Define a name and set the configuration options for the security realm. See Configuration Decisions When Creating a New Security Realm and Configure new security realms in the Administration Console online help.
  2. Configure the required security providers for the security realm. A valid security realm requires an Authentication provider, an Authorization provider, an Adjudication provider, a Credential Mapping provider, and a Role Mapping provider. Otherwise, you will not be able to set the new security realm as the default security realm. See Configuring WebLogic Security Providers, and Configuring Authentication Providers.
  3. Optionally, define Identity Assertion, Auditing, and Cert Registry providers. See Configuring WebLogic Security Providers, and Configuring Authentication Providers.
  4. If you configured the WebLogic Authentication, Authorization, Credential Mapping or Role Mapping provider or the Certificate Registry in the new security realm, verify that the settings of the embedded LDAP server are appropriate. See Managing the Embedded LDAP Server.
  5. Optionally, configure caches to improve the performance of the WebLogic or LDAP Authentication providers in the security realm. See Improving the Performance of WebLogic and LDAP Authentication Providers.
  6. Protect WebLogic resources in the new security realm with security policies. Creating security policies is a multi-step process with many options. To fully understand this process, read Securing WebLogic Resources. This document should be used in conjunction with Securing WebLogic Server to ensure security is completely configured for a WebLogic Server deployment.
  7. Protect user accounts in the new security realm from dictionary attacks by setting lockout attributes. See Protecting User Accounts and Protect user accounts in the Administration Console online help.
  8. Set the new realm as the default security realm for the WebLogic domain. See Change the default security realm in the Administration Console online help.

Note that you can also use the WebLogic Scripting Tool or Java Management Extensions (JMX) APIs to create a new security configuration. For information more information, see WebLogic Scripting Tool.

 

Skip navigation bar  Back to Top Previous Next