Right click and select System MBean Browser.

Handling Lifecycle Management Changes 12-15

12.3.5.5 Configuring SSL for Design Console

To change the Design console to establish secure connection between Oracle Identity Manager and Design console:

1. Add WebLogic server jars required to support SSL.

2. Copy webserviceclient+ssl.jar from: WL_HOMEserverlib to OIM_HOMEdesignconsoleext directory.

3. Use the Server trust store in the Design console. To access this:

a. Go to WebLogic Server Administrative console, Environment, Servers.

b. Click on OIM_SERVER_NAME to view details of the Oracle Identity

Manger server.

c. Click the KeyStores tab and note down the Trust keystore location in the

Trust section. If Design Console is Deployed on the Oracle Identity Manager Host Set the TRUSTSTORE_LOCATION environment variable to the location of the Trust keystore location noted above. For example: setenv TRUSTSTORELOCATIONscratchuser1dogwoodsh100520beahomewlserver_10. 3serverlibDemoTrust.jks If Design Console is Deployed on a Different Computer than Oracle Identity Manager Copy the Trust keystore to the box in which Design console is present and set the TRUSTSTORE_LOCATION env variable to the location where Trust keystore is copied on the local box.

12.3.5.6 Configuring SSL for Oracle Identity Manager Utilities

Oracle Identity Manager client utilities include PurgeCache, GenerateSnapshot, UploadJars, and UploadResources. Set the TRUSTSTORE_LOCATION environment variable to the location of the Trust keystore location. For example: setenv TRUSTSTORELOCATIONscratchuser1dogwoodsh100520beahomewlserver_10. 3serverlibDemoTrust.jks Note: Refer Configuring SSL for Design Console on page 12-15 for details about setting the TRUSTSTORE_LOCATION environment variable to the location of the Trust keystore location. 12-16 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

12.3.5.7 Configuring SSL for MDS Utilities

All Oracle Identity Manager MDS Utilities which contains WLST scripts must be set to the following environment variable in the shell in which you are running the script: WLST_PROPERTIES=-Dweblogic.security.SSL.ignoreHostnameVerification=true-Dwe blogic.security.TrustKeyStore=DemoTrust

12.3.5.8 Configuring SSL for SPMLCallback Domain

To configure SSL for SPMLcallback domain: 1. Ensure that Oracle Identity Manager port is SSL enabled with HostName verification set to false. 2. Enable SSL on Fusion Applications including callback domain. 3. If you are using WebLogic default trust store, you must not change anything other than enabling the SSL mode. 4. If you have certificates other than default, then the trusted certificates should be exchanged between them to establish two-way trust. See Signing the Certificates on page 12-10 and Exporting the Certificate on page 12-10 for information about signing and exporting certificates.

5. If you are using a stand-alone client for sending SPML requests for testing

purpose, then you must:

a. Add the following system properties to SPML client command to send the

request to SSL enabled OIM port. – Djavax.net.ssl.trustStore=D:\Oracle\Middleware1\wlserver_10.3\server\lib \DemoTrust.jks – -Djava.protocol.handler.pkgs=weblogic.net – -Dweblogic.security.TrustKeyStore=DemoTrust b. Add webserviceclient+ssl.jar to your client classpath. Note: Once this property is set, WLST works fine. You will see INFONOTICE messages, which you can ignore. See Also: Enabling SSL for Oracle Identity Manager By Using Custom Keystore on page 12-11 for information about enabling SSL for Oracle Identity Manager by using custom keystore See Also: Configuring SSL in the Oracle Fusion Middleware Securing Oracle WebLogic Server for detailed information about configuring SSL for Oracle WebLogic Server Note: Change the value of the Djavax.net.ssl.trustStore parameter to point to the truststore used to configure SSL. See Configuring SSL for Design Console on page 12-15 for information about the location of the trust store used in WebLogic to configure SSL.