Basic Authorization header missing in Outbound EAI HTTP Transport call
Last updated on APRIL 30, 2018
Applies to:Siebel eCommunications - Version 18.104.22.168 SIA and later
Siebel CRM - Version 22.214.171.124 and later
Information in this document applies to any platform.
*** Checked for currency MAY-22-2016 ***
***Checked for Relevance on Dec 29th 2017***
A custom workflow calls 'EAI HTTP Transport' (outbound HTTP). The external web servier is protected by Basic Authentication and it expects the credentials to be sent in the authorization header. URL sent from siebel :
It has been observed that some of the outbound requests from Siebel are failed to be processed as the external system did not receive the expected username/password.
For both the failing and successful scenarios, Siebel was sending to the correct URL. This was verified by checking the Input Argument of the 'EAI HTTP Transport' service from the Siebel component logs.
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