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
Last updated on DECEMBER 02, 2017
Applies to:Business Intelligence Server Enterprise Edition - Version 220.127.116.11.2 and later
Business Intelligence Suite Enterprise Edition - Version 18.104.22.168.2 and later
Information in this document applies to any platform.
***Checked for relevance on 01-Dec-2014***
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.
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