Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 5

Act as (Proxy user) Functionality

The act as functionality is a proxy authentication


functionality which authorises a user to act as an other
user when navigating in BI Presentation Service.

Configuration Steps:
Defining the Association Between Proxy Users and
Target Users.
You define the association between proxy users and
target users in the database by identifying, for each
proxy user/target user association, the:
ID of the proxy user
ID of the target user
Proxy level (either full or restricted). A Restricted level gives you only a read
access. Proxylevel value is case sensitive and must be all
lowercase.

CREATE
TABLE OBIEE_PROXY
(
PROXY_USER_ID
VARCHAR2(30 BYTE)
PROXY_TARGET_ID VARCHAR2(30 BYTE)
PROXY_LEVEL
VARCHAR2(10 BYTE)
CONSTRAINT OBIEE_PROXY_PK PRIMARY
PROXY_TARGET_ID )
ENABLE
)

NOT
NOT
NOT
KEY

NULL ,
NULL ,
NULL ,
( PROXY_USER_ID ,

For example, you might create a table called OBIEE_PROXY in


the database:

Its look like

Creating Session Variables for Proxy


Functionality:
There are two system session variables along with their
associated initialization blocks that you create to
authenticate proxy users:
PROXY
SELECT
PROXY_TARGET_ID
FROM
OBIEE_PROXY
WHERE
PROXY_USER_ID
= ':USER'
AND PROXY_TARGET_ID =
'VALUEOF(NQ_SESSION.RUNAS)'

PROXYLEVEL:
(optional) If you do not create
PROXYLEVEL, restricted access is assumed.
SELECT
PROXY_LEVEL
FROM
OBIEE_PROXY
WHERE
PROXY_USER_ID
= ':USER'
AND PROXY_TARGET_ID = 'VALUEOF(NQ_SESSION.RUNAS)'

Creating a Custom Message Template for Proxy


Functionality:
You need to create a custom
message template for the proxy functionality that
contains the SQL

The following entry is an example:

Modifying the instanceconfig.xml File for Proxy


Functionality:
You can modify the Oracle BI Presentation Services
configuration file (instanceconfig.xml) to specify the following information for
proxy functionality:

For example between the <ServerInstance> node, you


can insert:
<LogonParam>
<TemplateMessageName>LogonParamSQLTemplate</TemplateMessageName>
<MaxValues>100</MaxValues>
</LogonParam>

You might also like