Signing Policy Is Not Working For A client Connection Through OSB or SOA To a Particular Service
Last updated on SEPTEMBER 13, 2017
Applies to:Oracle Web Services Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Using a signing policy defined in OWSM for an OSB Business Service and a SOA Reference to a particular end service. From the service, the following error is being received:
"The Signature or decryption was invalid".
A similar setup is being created in SoapUI and this is working fine. Checked all the settings in both OWSM and SoapUI and no difference is noticed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms