OBIEE SSO Setup With SAML2 Doesn't Work getting " "HTTP 403 Forbidden" error or getting An Infinite Loop And Fails To Connect
(Doc ID 2022531.1)
Last updated on APRIL 05, 2023
Applies to:
Oracle WebLogic Server - Version 10.3.6 to 10.3.6Business Intelligence Server Administrator - Version 11.1.1.7.0 to 11.1.1.7.150714 [Release 11g]
Information in this document applies to any platform.
Symptoms
The issue happens every time an OBIEE Bundle Patch is applied to a working OBIEE environment where SAML2 SSO has been configured with OBIEE.
The login page goes into an infinite loop when customers use the URL as "/analytics/*" and it throws the following error if set it up as "/analytics/""
ceTypeFromURI(): request URI is '/analytics/default.jsp'>
#### <> <> <getServi
ceTypeFromURI(): request URI is not a service URI>
#### <> <> <getServi
ceTypeFromURI(): returning service type 'SPinitiator'>
#### <> <> ating authn request: processing>
#### <> <> get the partner name for the redirect URI [/analytics/default.jsp].>
or you see the following error:-
Error 403--Forbidden
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it.....
Changes
Applied an OBIEE Bundle Patch to a working OBIEE environment which has been configured with SAML2 SSO.
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 |
| Changes |
| Cause |
| Solution |
| References |