Grupie BIAdministratoras należy dodać polisę :oracle.bi.server.impersonateUsers
ORACLE DOC http://docs.oracle.com/cd/E23943_01/bi.1111/e10543/install.htm#CIHJEIEG
There will come a point in the lifecycle of an OBIEE deployment when one user will need to access another user’s account. This may be to cover whilst a colleague is on leave, or a support staff trying to reproduce a reported error.
Password sharing aside (it’s zero-config! but a really really bad idea), OBIEE supports two methods for one user to access the system as if they were another: Impersonation and Act As.
This blog article is not an explanation of how to set these up (there are plenty of blogs and rip-off blogs detailing this already), but to explain the difference between the two options.
First, a quick look at what they actually are.
Impersonation
Impersonation is where a “superuser” (one with
oracle.bi.server.impersonateUser application policy grant) can login to OBIEE as another user, without needing their password. It is achieved in the front end by constructing a URL, specifying:- The superuser’s login name and password (
NQUserandNQPasword) - The login ID of the user to impersonate (
Impersonate)
For example:
http://server:port/analytics/saw.dll?Logon&NQUser=weblogic&NQPassword=Password01&Impersonate=FSmith_FundY
