My Oracle Support Banner

Configuring a DB-based KSS keystore For Use With WCC 12c Web Services (Doc ID 2523647.1)

Last updated on JULY 20, 2024

Applies to:

Oracle WebCenter Content - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Goal

In Oracle WebCenter Content (WCC) 12c, the GenericSoapService (GenericSoapPort) Web service can be used to call WCC services.  By default, the service does not have WS-Security applied, but WS-Security can be set through the use of web service policies (WS-Policy). Security policies can be set to web services in order to define their security protocol. In particular, the Oracle WCC web services support OWSM policies.

Some general classes of policies are supported: username-token, and SAML. The following is a list of supported OWSM policies:

    oracle/wss11_saml_token_with_message_protection_service_policy
    oracle/wss11_username_token_with_message_protection_service_policy
    oracle/wss_username_token_service_policy
     oracle/wss_http_token_service_policy
     oracle/wss_http_token_over_ssl_service_policy

However in WCC 12c, the keystore in WLS domain are configured to use KSS (Oracle Key Store Service) and Oracle Database  as default.

So, this document describes a "sample" steps to configure the keystore for using Oracle WCC web services with the OWSM policies with the default keystore configuration.

Note:
See <Document 1456506.1> for 11g, using file-based JKS keystore.

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Prerequisite
 Steps
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.