Using Oracle Adaptive Access Manager Shared Library in Enterprise Applications

4-2 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager library-nameoracle.oaam.libslibrary-name library-ref

4.1.3 CustomizingExtendingOverriding Oracle Adaptive Access Manager Properties

To override any Oracle Adaptive Access Manager properties or extend Oracle Adaptive Access Manager enumerations, add those properties and enumerations to bharosa_server.properties and place that file in WEB-INF\classes folder of the native web application. For instructions on customizing, extending, or overriding Oracle Adaptive Access Manager properties, refer to Chapter 7, Customizing Oracle Adaptive Access Manager.

4.2 OAAM Java InProc Integration

Follow these steps: 1. Make sure you have set the reference to OAAM shared library oracle.oaam.libs. 2. To override any Oracle Adaptive Access Manager properties or extend Oracle Adaptive Access Manager enumerations, add those properties and enumerations to bharosa_server.properties and place that file in the WEB-INF\classes folder of the native web application. 3. Set up OAAM Data Source with the JNDI name as jdbcOAAM_SERVER_DB_DS and point it to the OAAM database.

4.3 OAAM SOAP Integration

To call the OAAM APIs via SOAP instead of inproc, follow these steps in these sections.

4.3.1 Set up SOAP Security

Setup SOAP User on WebLogic Server and OWSM Policy Out-of-the-box, OAAM publishes Web services at the URL: oaam_ serverservices. This URL is protected with HTTP Basic authentication. Create a user that will be used for SOAP authentication, and add that user in the proper group. This user can access this URL. The user must be in the OAAMSOAPServicesGroup group. To set up the OWSM Policy to set HTTP Basic Authentication on oaam_ serverservices follow these steps: 1. Log in to Enterprise Manager using the URL http:weblogic-admin-hostname:portem. 2. Under weblogic_domain, select the domain and select oaam_server_ server1 under that and right click and select the Web Services option. 3. Click the Attach Policies link in top right area.

4. Select all the rows corresponding to OAAM Web Services and click the Next

button 5. To enable SOAP Authentication: Integrating Native Java Applications 4-3

a. Select the row oraclewss_http_token_service_policy.

6. To disable SOAP Authentication:

a. Select the rows oraclebinding_authorization_permitall_policy, oracleno_

authentication_service_policy , oracleno_authorization_service_policy and click the Next button

7. Click the Attach button in the next page.

8. Restart OAAM Server if required. Client Side Keystore to secure the SOAP User password Web ServicesSOAP clients need to send the username and password for successful communication with OAAM web services. 1. In the ORACLE_HOMEoaamcli directory, create a file, for example, soap_ key.file, and enter the HTTP authentication user password in it. The password from the user that was added to the OAAMSOAPServicesGroup rolegroup. 2. Copy sample.soap_3des_input.properties to soap_3des_ input.properties. 3. Update soap_3des_input.properties with the keystore password, the alias password, and password file. This is the password for opening the keystore. keystorepasswd= This is the password reading alias key in the keystore keystorealiaspasswd= File containing from key. Please note, keys in AES could be binary. Also note algorithms like 3DES require minimum 24 characters in the key keyFile=soap_key.file keyFile= 4. Generate the keystore. ■ For UnixLinux, run JAVA_EXE -Djava.security.policy=confjmx.policy -classpath CLSPTH com.bharosa.vcrypt.common.util.KeyStoreUtil updateOrCreateKeyStore readFromFile=soap_3des_input.properties ■ For Windows, run genkeystore.cmd soap_3des_input.properties If the KeyStore command was successful, you will see output similar to the following: updateOrCreateKeyStore done Keystore file:system_soap.keystore,algorithm=DESede KeyStore Password=ZG92ZTEyMzQ= Alias Password=ZG92ZTEyMw== 5. Note down the Keystore password and Alias Password print on the screen. You will need to add these to bharosa_server.properties. 6. Save the system_soap.keystore file in your source code control system. Please take adequate security precaution while handling this file. The file contains critical password information. Make sure that only authorized personnel have read access