Access Controls for Profiles

2-4 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform

2.3 Data Integrity and Oracle Directory Integration Platform

Oracle Directory Integration Platform ensures that data is not modified, deleted, or replayed during transmission by using SSL. This SSL feature generates a cryptographically secure message digest—through cryptographic checksums using either the Message-Digest algorithm 5 MD5 or the Secure Hash Algorithm SHA —and includes the message digest with each packet sent across the network.

2.4 Data Privacy and Oracle Directory Integration Platform

Oracle Directory Integration Platform ensures that data is not disclosed during transmission by using public-key encryption available with SSL. In public-key encryption, the sender of a message encrypts the message with the public key of the recipient. Upon delivery, the recipient decrypts the message using the recipients private key. To exchange data securely between the directory integration server and Oracle Internet Directory, you must run both components in the same SSL mode.

2.5 Tools Security and Oracle Directory Integration Platform

You can run all the commonly used tools in SSL mode to transmit data to Oracle Internet Directory securely, including Oracle Enterprise Manager Fusion Middleware Control.

2.6 Credential Storing

Oracle Directory Integration Platform uses the Credential Store Framework of the Oracle Application Server 11g infrastructure. The following is a list and description of the credentials Oracle Directory Integration Platform stores in this Credential Store Framework: ■ The Oracle Directory Integration Platform user password. The password is created during installation, stored as read-only, and read by run-time operations. ■ The JKS password. The JKS password is used if the Server Only mode 2 SSL setting is configured for connecting to Oracle Internet Directory or a third-party directory. You can use the WebLogic Scripting Tool WLST createCred command to write the keystore password to the Credential Store Framework. For example: after invoking the WLST shell and connecting to the Oracle WebLogic Admin Server using the connect command, enter: createCredmap=dip, key=jksKey, type=PC, user=userName, password=password The map and key options are fixed—the only supported values are map=dip and key=jksKey. You can use the wlst listCred command to view the keystore password in the Credential Store Framework. For example: after invoking the WLST shell and connecting to the Oracle WebLogic Admin Server using the connect command, enter: listCredmap=dip, key=jksKey Security Features in Oracle Directory Integration Platform 2-5 See Also: ■ The Oracle Fusion Middleware Security Guide for complete information about the Credential Store Framework of the Oracle Application Server 11g infrastructure. ■ The Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for more information about the wlst commands.