When you use the Embedded LDAP that is supplied by Oracle WebLogic Server, which three
statements are true?
A.
The Embedded LDAP can be used to store user, group, security roles and security policies for
the WebLogic security providers.
B.
The Embedded LDAP uses the file system to store Weblogic security provider data.
C.
The Embedded LDAP can be accessed by an external LDAP viewer.
D.
The Embedded LDAP cannot be used in a production environment
E.
The Embedded LDAP can store Auditing Data.
Explanation:
A: The embedded LDAP server contains user, group, group membership, security
role, security policy, and credential map information.
C: The credential (usually a password) used to connect to the embedded LDAP server. If this
password has not been set, WebLogic Server generates a password at startup, initializes the
attribute, and saves the configuration to the config.xml file. If you want to connect to the embedded
LDAP server using an external LDAP browser and the embedded LDAP administrator account
(cn=Admin), change this attribute from the generated value.
E: You can use either the WebLogic Auditing provider or a custom Auditing provider in a securityrealm. Although an Auditing provider is configured per security realm, each server writes auditing
data to its own log file in the server directory. By default, all auditing information recorded by the
WebLogic Auditing provider is saved in the following file:
WL_HOME\yourdomain\yourserver\DefaultAuditRecorder.log.
By writing a custom Auditing provider, however, you can send the records containing audit
information to any one of various output repositories, such as an LDAP server, database, or a
simple file.