If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the left
pane, select Security Realms.
All the security
realms available for the WebLogic domain are listed in the Realms
Create a New Realm page, enter the name of the new security
You have the
option of loading credential maps from weblogic-ra.xml deployment
descriptor files into the embedded LDAP server and then using the
WebLogic Server Administration Console to create new credential maps
or modify existing credential maps.
Once information from
deployment descriptor file is loaded into the embedded LDAP server,
the original resource adapter remains unchanged. Therefore, if you
redeploy the original resource adapter (which will happen if you
redeploy it through the WebLogic Server Administration Console,
modify it on disk, or restart WebLogic Server), the data will once
again be imported from the weblogic-ra.xml deployment
descriptor file and credential mapping information may be lost.
To avoid overwriting
new credential mapping information with old information in a weblogic-ra.xml deployment
descriptor file, select the Ignore Deploy Credential Mapping
use load credential maps into the embedded LDAP server, the
Credential Mapping provider in the security realm must have the
Credential Mapping Deployment Enabled attribute checked. For more
information, see Configure Credential
In the Administration Console's Change Center, click
the required security providers for the security realm. In order for a
security realm to be valid, you must configure 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. For more information, see Manage security
define an Identity Assertion and Auditing provider.