How To Ensure HTTPS URLs Are Inserted Into OSB Response WSDLs Instead Of HTTP URLs To Avoid HTTP 403 Forbidden Error When HTTPS Required?
Last updated on MAY 23, 2017
Applies to:Oracle Service Bus - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Can we maintain our current infrastructure configuration, while at the same time generating HTTPS URLs back to the client, that they can then use to get back in with, for service calls?
What is happening in the current configuration, is that Client accesses the OSB proxy service WSDL using HTTPS, and the WSDL that the client gets back have HTTP URLs instead of HTTPS URLs.
Step 1: Client accesses OSB Proxy WSDL URL over HTTPS as:
Step 2: Client gets the response back, with HTTP URLs that OSB Proxy generates for the schema files and puts in the WSDL document.
These HTTP URLs cause problems for the client when they try to use them to get back into the system, as it times out due to it being HTTP and not HTTPS as expected.
When manually changed to HTTPS, then it works as expected, but we cannot ask the client to change it manually, so a way to have OSB return these URLs as HTTPS and not HTTP is needed.
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