...
- Essbase Authentication plugin with SSO mode enabled
- Use User Impersonation (recommended approach)
Essbase Authentication plugin with SSO mode enabled
...
The user impersonation scenario can be used to overcome the limitations of the Essbase Authentication plugin scenario.
In this case, the connection to Essabase servers is made using the username and password configured in CXO Software on behalf of the the end user logged in to CXO. In this case the Essbase API function "LoginAs" is used to open the connection.
...
- Start the Source system manager (if you want to check if the connection is working you need to login with a cxo user, that also exists in Essbase)
- Select the Essbase source system
- Click Connector Properties
- Under SSO Login, check Impersonate User
Essbase logs in case of impersonation
The way How Essbase logs activities from "EssLoginAs" functionality is managed by Oracle.
Based on tests performed by CXO, Essbase logs the impersonated user, and not the service account when we retrieve data (Mdx queries).
Below is an example from Essbase log when "EssLoginAs" functionality is used. In the use case below the Impersonated username is Julien.
[Mon Jun 14 07:11:10 2021]Local/ASOsamp///2052/Info(1042059)
Connected from [::ffff:172.31.35.177]
[Mon Jun 14 07:11:10 2021]Local/ASOsamp/Sample/Julien@Native Directory/2052/Info(1013091)
Received Command [MdxReport] from user [Julien@Native Directory]
[Mon Jun 14 07:11:10 2021]Local/ASOsamp/Sample/Julien@Native Directory/2052/Info(1260039)
MaxL DML Execution Elapsed Time : [0.031] seconds
[Mon Jun 14 07:11:10 2021]Local/ASOsamp///2280/Info(1042059)
Connected from [::ffff:172.31.35.177]
[Mon Jun 14 07:11:10 2021]Local/ASOsamp/Sample/Julien@Native Directory/2280/Info(1013091)
Received Command [MdxReport] from user [Julien@Native Directory]
[Mon Jun 14 07:11:10 2021]Local/ASOsamp/Sample/Julien@Native Directory/2280/Info(1260039)
MaxL DML Execution Elapsed Time : [0] seconds