My Oracle Support Banner

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 MAY 26, 2022

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.


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

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

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




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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