Siebel Application Users Are Sporadically Getting HTTP 403 Errors While Accessing Siebel Application URLs (Doc ID 3063819.1)

Last updated on DECEMBER 23, 2024

Applies to:

Symptoms

Some users are receiving HTTP 403 error when trying to access the Siebel application on Production environment.

This started last Wednesday 12/11/2024 with no known changes on the Siebel configuration nor on LBaaS setup.

The web layer is setup as follows:

  LBaaS <-> two proxy servers <-> two AI servers

User experience is as follows:

  - users getting the HTTP 403 error cannot access the Siebel application even if they clear the browser cache
  - users who don't get the HTTP 403 error can access the Siebel application without issues

The HTTP 403 is not passing through to Siebel logs.

STEPS

1. End user tries to access any of the mentioned URLs above
2. If the user gets HTTP 403 he/she cannot access the Siebel application
3. if the user doesn't get HTTP 403 error he/she can access the Siebel application as normal 

Changes

No known changes on the Siebel configuration nor on LBaaS setup.

Cause

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