Siebel Outbound REST Call Fails With HTTP 'Status code - 401' Error Due To Authorization Header Reset From Mixed Case "Authorization" To Lower Case "authorization" By SES ApplicationContainer_Internal Layer (Doc ID 2871862.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

An Outbound REST service has been created in Siebel 22.1 version.  When using Siebel application to invoke the Outbound REST API call, an HTTP 'Status code - 401' occurs.

The error message that occurs and shows up in the Siebel Client UI AOM log file is:

The behaviour occurs as follows:

1. Configure Siebel application to send outbound requests to an external system.

The instructions from the following documentation was followed to perform initial configure/set up step:

Siebel Bookshelf > REST Guide > Chapter 12 Using Siebel REST Outbound Services > Invoking the External REST Service Endpoint Using Proxy Business Service at Runtime

https://docs.oracle.com/cd/F26413_28/books/RestAPI/c-Invoking-External-REST-Service-Endpoint.html#c_Invoking_External_REST_Service_Endpoint

2. Log into Siebel application and invoke the outbound API call

3. The request fails with the reported http 401 error at this point.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.