Proxy with BI EE
By bryan.wise on Jun 03, 2008
A customer request came through the other day that I thought was worth writing about. They were using BIP with BI EE as a data source. They were also using Business Model Filters in BI EE based on the user's identity. Their concern came in how BI EE was accessed as a data source. They had setup the BI Server as a JDBC data source and used Administrator as the credential. (This data source gets setup automatically on a standard BI EE install.) They did not want the SQL being sent to the BI Server to run as Administrator. This would bypass the Business Model Filters that they had designed into their BI EE metadata. No problem.
They way to solve this is to make sure that when you define a connection to the BI Server, that you check the little box that says "Use Proxy Authentication." I just checked a fresh 10.1.3.3.3 install and this is even checked by default during the installation--which is great: you're all set. (I'm not sure if older versions did that as well...)
Let's just do some quick verification.
First make sure your data source is setup correctly:
Now create a query that is end user sensitive. This Could be a query that will cause a Business Model Filter to be applied by the BI Server. In my case, I kept this simple and just created a query that referenced the session variable "USER". This will tell us that the BI Server knows who is really issuing the query.
If I run this as Administrator, I see that the BI Server thinks Administrator is running the query:
If I run this same report as an end user called "env", I see that the BI Server thinks "env" is running the query even though BIP is connecting to the BI Server using Administrator's credentials.
In conclusion, we see that the "use Proxy Authentication" check box does work. BIP connects using Administrator's credentials, but properly tells the BI Server who is really running the query.