Configuring Oracle WebCenter Content for Oracle Identity Cloud Service (IDCS)



Configuring WebCenter Content for Oracle Identity Cloud Service (IDCS) on OKE. Configuration information is provided in the following sections:

  • Updating SSL.hostnameVerifier Property
  • Configuring IDCS Security Provider
  • Configuring WebCenter Content for User Logout

Updating SSL.hostnameVerifier Property

To update SSL.hostnameVerifier property, do the following: This is necessary for the IDCS provider to access IDCS.

  1. Stop all the servers in the domain including Administration server and all Managed WebLogic servers.

  2. Update the SSL.hostnameVerifier property:

    edit the file <DOMAIN_HOME>//bin/ go to pv location file system and modify the file sample: /WCCFS/wccinfra/bin/


    Alternatively create or modify the file <DOMAIN_HOME>/<domain_name>/bin/ Add the SSL.hostnameVerifier property for the IDCS Authenticator: sample: /WCCFS/wccinfra/bin/

  3. Start the Administration server and all Managed WebLogic servers.

Configuring IDCS Security Provider

  1. Log in to the IDCS administration console.

  2. Create a trusted application. In the Add Confidential Application wizard:

    1. Enter the client name and the description (optional).
    2. Select the Configure this application as a client now option. To configure this application, expand the Client Configuration in the Configuration tab.
    3. In the Allowed Grant Types , select Client Credentials field the check box.
    4. In the Grant the client access to Identity Cloud Service Admin APIs section, click Add to add the APP Roles (application roles). You can add the Identity Domain Administrator role.
    5. Keep the default settings for the pages and click Finish.
    6. Record/Copy the Client ID and Client Secret.This is needed when you will create the IDCS provider.
    7. Activate the application.

Configuring Oracle Identity Cloud Integrator Provider

To configure Identity Cloud Integrator Provider:

  1. Log in to the WebLogic Server Administration console.

  2. Select Security Realm in the Domain Structure pane.

  3. On the Summary of Security Realms page, select the name of the realm (for example, myrealm). Click myrealm. The Settings for myrealm page appears.

  4. On the Settings for Realm Name page, select Providers and then Authentication. To create a new Authentication Provider, in the Authentication Providers table, click New.

  5. In the Create a New Authentication Provider page, enter the name of the authentication provider, for example, IDCSIntegrator and select the OracleIdentityCloudIntegrator type of authentication provider from the drop-down list and click OK.

  6. In the Authentication Providers table, click the newly created Oracle Identity Cloud Integrator, IDCSIntegrator link.

  7. In the Settings for IDCSIntegrator page, for the Control Flag field, select the Sufficient option from the drop-down list Click Save.

  8. Go to the Provider Specific page to configure the additional attributes for the security provider. Enter the values for the following fields & Click Save:

    • Host
    • Port 443(default)
    • select SSLEnabled
    • Tenant
    • Client Id
    • Client Secret.

    NOTE: If IDCS URL is, then IDCS host would be and tenant name would be idcs-abcde. Keep the default settings for other sections of the page.

  9. Select Security Realm, then myrealm, and then Providers. In the Authentication Providers table, click Reorder.

  10. In the Reorder Authentication Providers page, move IDCSIntegrator on the top and click OK.

  11. In the Authentication Providers table, click the DefaultAuthenticator link. In the Settings for DefaultAuthenticator page, for the Control Flag field, select the Sufficient option from the drop-down list. Click Save.

  12. All changes will be activated. Restart the Administration server.

Setting Up Trust between IDCS and WebLogic

To set up trust between IDCS and WebLogic

  1. Import certificate in KSS store.
    • Run this from the Administration Server node.
    • Get IDCS certificate:
      echo -n | openssl s_client -showcerts -servername <IDCS_URL> -connect <IDCS_URL>:443|sed -ne '/-BEGIN CERTIFICATE-/,/-END
      CERTIFICATE-/p' > /tmp/idcs_cert_chain.crt     
      echo -n | openssl s_client -showcerts -servername -connect|sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /tmp/idcs_cert_chain.crt
      #copy the certificate inside the admin_pod
      kubectl cp /tmp/idcs_cert_chain.crt wccns/xyz-adminserver:/u01/idcs_cert_chain.crt
    • Import certificate. Run <ORACLE_HOME>/oracle_common/common/bin/ file.
      svc=getOpssService(name='KeyStoreService')        svc.importKeyStoreCertificate(appStripe='system',name='trust',password='',alias='idcs_cert_chain',type='TrustedCertificate',filepath='/tmp/idcs_cert_chain.crt',keypassword='')
      wls:/offline> connect('weblogic','welcome','t3://xyz-adminserver:7001')
      wls:/wccinfra/serverConfig/> svc=getOpssService(name='KeyStoreService')
    • exit()
  2. Restart the Administration server and Managed servers

Creating Admin User in IDCS Administration Console for WebCenter Content

It is important to create the Admin user in IDCS because once the Managed servers are configured for SAML, the domain admin user (typically weblogic user) will not be able to log into the Managed servers.

To create WebLogic Admin user in IDCS for WebCenter Content JaxWS connection:

  1. Go to the Groups tab and create Administrators and sysmanager roles in IDCS.
  2. Go to the Users tab and create a wls admin user, for example, weblogic and assign it to Administrators and sysmanager groups.
  3. Restart all the Managed servers.

Managing Group Memberships, Roles, and Accounts

This will require modifying OPSS and libOVD to access IDCS. The following steps are required if using IDCS for user authorization. Do not run these steps if you are using IDCS only for user authentication. Ensure that all the servers are stopped (including Administration) before proceeding with the following steps:

NOTE: Shutdown all the servers using WebLogic Server Administration Console. Please keep in mind - kubectl patch domain command is the recommended way for starting/stopping pods. Please refrain from using WebLogic Server Administration Console for the same, anywhere else.

  1. Run the following script:

    #exec the Administration server
    kubectl exec -n wccns -it wccinfra-adminserver -- /bin/bash
    #Run the
    cd /u01/oracle/oracle_common/common/bin/

    NOTE: It’s not required to connect to WebLogic Administration Server.

  2. Read the domain:

    wls:/offline> readDomain('/u01/oracle/user_projects/domains/wccinfra')
  3. Add the template:


    NOTE: This step may throw a warning, which can be ignored. The addTemplate is deprecated. Use selectTemplate followed by loadTemplates in place of addTemplate.

  4. Update the domain:

    wls:/offline/wccinfra> updateDomain()
  5. Close the domain:

    wls:/offline/wccinfra> closeDomain()
  6. Exit from the Administration server container:

  7. Start the servers (Administration and Managed).

Configuring WebCenter Content for User Logout

If the Logout link is selected, you will be re-authenticated by SAML. To be able to select the Logout link:

  1. Log in to WebCenter Content Server as an administrator. Select Administration, then Admin Server, and then General Configuration.
  2. In the Additional Configuration Variables pane, add the following parameter:
  3. Click Save.
  4. Restart the Administration and Managed servers.