OBIEE 11g: How To Set OAM Rules to Allow GO URL or Action Links to Open a Public Facing Dashboard when Using OBIEE with OAM and SSO
(Doc ID 1520138.1)
Last updated on JANUARY 30, 2022
Applies to:Business Intelligence Server Enterprise Edition - Version 22.214.171.124.2 and later
Business Intelligence Suite Enterprise Edition - Version 126.96.36.199.2 and later
Information in this document applies to any platform.
You have an internal website protected by OAM rules and SSO. You want to provide an external Dashboard using a GO URL or Action Link including NQUser and NQPassword to authenticate through Oracle OAM.
OAM set up needs to provide certain rules for protected OBIEE URLs and public-facing URLs. OAM requires authentication to the OBIEE rendering engine resources. This is because OAM has a policy that is explicitly protecting the OBIEE rendering engine. This works when you can authenticate. However, if you are an anonymous user accessing a public, internet-facing application, you are challenged for credentials you do not have. Thus you cannot see, nor interact, with the reports and dashboard because you are not authorized.
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