Configuring a DB-based KSS keystore For Use With WCC 12c Web Services
(Doc ID 2523647.1)
Last updated on JULY 25, 2019
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
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.
Two general classes of policies are supported: username-token, and SAML. The following is a list of supported OWSM policies:
If one of these policies apply to the UCM web service, a keystore must be created. The steps to configure it as a file-based keystore are described in the following document.
Oracle Fusion Middleware Developing with Oracle WebCenter Content 12c (184.108.40.206.0) (E85757-04)
26 Configuring WebCenter Content Web Services for Integration
26.2 Configuring Web Service Security Through Web Service Policies
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.
See <Document 1456506.1> for 11g, using file-based JKS keystore.
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