Basic Authorization header missing in Outbound EAI HTTP Transport call (Doc ID 1335640.1)

Last updated on JULY 20, 2016

Applies to:

Siebel eCommunications - Version 7.8.2.14 SIA[19251] and later
Siebel CRM - Version 7.8.2.14[19251] and later
Information in this document applies to any platform.
*** Checked for currency MAY-22-2016 ***

Symptoms

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 :

http://URY_CRMG:URY_CRMG00@xx.yy.zz.mm:port/invoke/SiebelGW_AddRedemptionProduct.Outbound.Services:processRequest?


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.

Cause

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