BI Publisher (MOSC)

MOSC Banner

Issue when specifying the BIPDataSource property of ReportRequest

edited Oct 7, 2013 11:19AM in BI Publisher (MOSC) 3 commentsAnswered
In the documentation for how to integrate BI Publisher reports with Virtual Private Databases (VPD) it suggests that the correct approach is to define "proxy authentication" on the data source definition. By doing that, the WebLogic user id of the person running the report (aka "xdo_user_name") is passed into the database, where it can be accessed by VPD policy functions.

While it was an administrative hassle, I have been able to figure out how to do that. However, there is a problem: the "proxy authentication" option is only available when defining a report data source through the BI Publisher administration UI. If you attempt to set database credentials at run-time using a "JDBCDataSource" object via the "ReportRequest.setDynamicDataSource" method, then there is no way to specify that the data source should use the "proxy authentication" option.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center