SAML2Exception: [Security:096572]The user is accessing the Idp initiator service, but not authenticated yet (Doc ID 1932592.1)

Last updated on AUGUST 03, 2017

Applies to:

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

Symptoms

Weblogic is configured as the identity provider for for a web application.
But, when one tries to call the service configured using the identity provider initiated URL, one can see the following error in the weblogic server log file:

####<Sep 24, 2014 3:08:34 PM EDT> <Debug> <SecuritySAML2Service> <machine-name> <server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1411585714155> <BEA-000000> <[Security:096572]The user is accessing the Idp initiator service, but not authenticated yet.>
####<Sep 24, 2014 3:08:34 PM EDT> <Debug> <SecuritySAML2Service> <machine-name> <server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1411585714155> <BEA-000000> <exception info
com.bea.security.saml2.service.SAML2Exception: [Security:096572]The user is accessing the Idp initiator service, but not authenticated yet.
at com.bea.security.saml2.service.sso.SSOServiceProcessor.doInitiator(SSOServiceProcessor.java:240)
at com.bea.security.saml2.service.sso.SSOServiceProcessor.process(SSOServiceProcessor.java:97)
at com.bea.security.saml2.service.sso.SingleSignOnServiceImpl.process(SingleSignOnServiceImpl.java:50)

...
...

and one gets a 403-Error message in the browser.

Changes

 

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