My Oracle Support Banner

SAML:Third Party IDP Configuration Causes Client Browser Goes to Infinite Loop (Doc ID 2252623.1)

Last updated on AUGUST 01, 2023

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

When trying to configure SSO for ORMB - Oracle Financial Services Revenue Management and Billing application using Weblogic as SP and OKTA as IDP the request is going to infinite loop. OKTA is the name of the Third Party IDP.

In the Weblogic Server SAML debug logs captured at the issue time, we can see that request URI from IDP is unable to resolve saying "request URI is not a service URI" and looping is observed at front end browser.

###<Mar 21, 2017 6:07:00 PM EDT> <Debug> <SecuritySAML2Service> <MACHINE_NAME> <SERVER_NAME> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <> <BEA-000000> <SAML2Filter: Processing request on URI '/ouaf/cis.jsp'>
####<Mar 21, 2017 6:07:00 PM EDT> <Debug> <SecuritySAML2Service> <MACHINE_NAME> <SERVER_NAME> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <> <BEA-000000> <getServiceTypeFromURI(): request URI is '/ouaf/cis.jsp'>
####<Mar 21, 2017 6:07:00 PM EDT> <Debug> <SecuritySAML2Service> <MACHINE_NAME> <SERVER_NAME> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <> <BEA-000000> <getServiceTypeFromURI(): request URI is not a service URI>
####<Mar 21, 2017 6:07:00 PM EDT> <Debug> <SecuritySAML2Service> <MACHINE_NAME> <SERVER_NAME> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <> <BEA-000000> <getServiceTypeFromURI(): returning service type 'SPinitiator'>
####<Mar 21, 2017 6:07:00 PM EDT> <Debug> <SecuritySAML2Service> <MACHINE_NAME> <SERVER_NAME> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <> <BEA-000000> <SP initiating authn request: processing>
####<Mar 21, 2017 6:07:00 PM EDT> <Debug> <SecuritySAML2Service> <MACHINE_NAME> <SERVER_NAME> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <> <BEA-000000> <SP initiating authn request: partner id is null>

 

Cause

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
Symptoms
Cause
Solution


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