Custom OWSM Class Unable To Retrieve Certificates Used By Container For Signing
(Doc ID 2791154.1)
Last updated on JULY 19, 2021
Applies to:Oracle Web Services Manager - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
A custom OWSM assertion with associated java classes is being used that among other things, signs different header elements in the outbound request when invoked via OSB.
This was developed in 11g (126.96.36.199). The custom OWSM class was modeled after a couple of blog articles (https://technology.amis.nl/2011/04/21/owsm-custom-assertion-part-1-setting-up-the-basic-structure/, https://technology.amis.nl/2011/05/18/owsm-custom-x509-assertion-part-2-creating-outgoing-client-assertion/) that shared how to access the credential store and keystore to use our SSL certificate to sign the header elements.
We are now trying to migrate to 12c (188.8.131.52) but for this OWSM policy, it will no longer compile due to changes to the underlying OWSM classes it referenced.
What are the code changes necessary to get this functionality in 12c?
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