Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 77 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
How to bypass SSO for a public user/password to display BI analysis - 12c
In 11c, we could bypass SSO by appending &NQUser and &NQPassword to the analytics URL when the dashboard was specified. Here's an example below:
This allowed us to put a public analysis on a public website effectively bypassing SSO. Note the above URL was called by another URL to hide the user and password that we were using!
We are now upgrading to 12c and this is no longer supported (when we attempt it, it sends us back to the OBI signon screen.)
Has anyone else encountered and solved this?
MOS suggested using BI WebServices, but I'm not sure that that will allow for the display of the Chart and pivot table to the user.
Webservices are normally a machine to machine implementation strategy.
All we want to have is the same ability as we had in 11g.
Any and all comments are welcome... We need to have this working in a few weeks.
Thanks...
Joel
Answers
-
One way to overcome this issue is to deploy a second analytics deployment in weblogic. This 2nd analytics deployment won't have any of the SSO configuration in it and should allow you to access OBIEE without SSO.
0 -
That was dropped because it actually was a security hole and should not have remained open.
As Joel said you would need a second deployment which doesn't use SSO.
0 -
Sounds interesting... Does anyone have a procedure to do this?
Very interested...
Joel
0 -
I’m wondering if that means doing two installs of OBI on the same or separate machines…
Since security is at the weblogic level, I would assume that you would then need two adminservers.
Seems like a lot of overkill for one small public app. Please respond..
0 -
I’ll look for some documentation to pass on about deploying a copy of the analytics application in Weblogic.
As @Christian said using NQUser & NQPassword in URLs is no longer allowed.
EDIT:
0 -
Joel Saunders wrote:Seems like a lot of overkill for one small public app. Please respond..
You want the opposite of SSO - no security at all. You can't ask your bank to have all your money in the world's safest vault and at the same time ask them to have free access through a second door and expect that to be an easy or logical request either.
0
