MicroStrategy Personas and SAP HANA User Defined Roles

• Strategy

This article provides a detailed example of how SAP HANA User Defined Roles can apply to MicroStrategy

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
Strategy allows you to leverage SAP HANA's database concept of User Defined Roles. User Defined Roles conveniently handle privileges of users using the database.

Example of How to Use User Defined Roles

Create a mock dataset. For example, create a
```
MOCK_DATA
```
table and a
```
MOCK_VIEW
```
view.

Create two users on SAP HANA. For example,
```
TEST_USER1 
```
and
```
TEST_USER2
```
.

Create privileges for your SAP HANA users.

Grant Analytical privileges to
```
TEST_USER2
```
.

Note: The concept of Roles is not used in this example due to the small number of users involved. Creating a Role and assigning it to a SAP HANA user will result in the same behavior.
Create a corresponding database instance, database connection, and database login for
```
TEST_USER1
```
,
```
TEST_USER2
```
, and the
```
HANA SYSTEM user
```
, who is present by default in Developer.

Create
```
TEST_USER1
```
and
```
TEST_USER2
```
in Strategy and open the User Editor. Navigate to Authentication > Warehouse and provide SAP HANA credentials for
```
TEST_USER1
```
and
```
TEST_USER2
```
.

Open Strategy Web and log in as the Strategy Administrator. Create a live cube connected to a SAP HANA database using the
```
__HANA_SYSTEM
```
data source.
Based on the privileges assigned to each user,
```
TEST_USER1
```
should see
```
SAP HANA 
```
tables in
```
MOCK_SCHEMA
```
, but is not able to add them to the project, whereas
```
TEST_USER2
```
can see and use the data due to their
```
CONTENT_ADMIN
```
privileges.

To see the
```
MOCK_VIEW
```
view created on SAP HANA, click Edit Catalog Options.

Uncheck the User default value checkbox and change the default entry
```
#LOGIN_NAME#
```
to
```
MOCK_SCHEMA
```
.

Use the search bar to find
```
MOCK_VIEW
```
and all all of its tables to the project. Click Execute SQL, then Finish.

Save the cube as
```
MOCK_VIEW_CUBE
```
in the Personal Objects folder.
Create a dossier from the cube and save it in Shared Reports.

Share the dossier to
```
TEST_USER1
```
and
```
TEST_USER2.
```
Review what SAP HANA privileges your users have by running the
```
MOCK_VIEW_DOSSIER
```
as a Strategy Administrator (the
```
HANA SYSTEM
```
user).

From the data returned, you can see that
```
TEST_USER2
```
has different privileges on the SAP HANA database than the
```
HANA SYSTEM
```
user.
Log out as the Administrator and log in to Web as
```
TEST_USER2
```
. The
```
MOCK_VIEW_DOSSIER
```
is available and editable to
```
TEST_USER2
```
due to their FULL ACCESS privilege.
Run the same dossier and notice the difference in returned results.

As a result of these steps, the Strategy user is now using the User Defined Roles defined on SAP HANA:
The HANA SYSTEM user corresponds to the Strategy Administrator (MSTR User), which can reflect the Application Architect persona.
TEST_USER2 (the same name in Strategy and in the HANA database) translates to a Project Architect who builds dossiers, but has limited access to data present on SAP HANA.

Comment

0 comments

Details

Knowledge Article

Published:

July 25, 2019

Last Updated:

March 21, 2024