Hitachi Vantara Pentaho Community Wiki
Child pages
  • 06. Adding Row Level Security to a Pentaho Metadata Model

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Example of Role Based Constraints

Wiki MarkupThis example defines an MQL Formula for three different roles.    The Admin Role has full row visibility, the Sales and Engineering Roles may only see data that joins to rows with their particular department. (The syntax is \ [business_table.business_column\] = value).

Role

Constraint

Admin

TRUE()

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a738ef30-e6f9-4c63-8e45-ad3b2d871f33"><ac:plain-text-body><![CDATA[

Sales

[BT_OFFICE.BC_DEPARTMENT]="Sales"

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ea634bbf-0adc-442b-a4ce-09902f46bef8"><ac:plain-text-body><![CDATA[

Engineering

[BT_OFFICE.BC_DEPARTMENT]="Engineering"

]]></ac:plain-text-body></ac:structured-macro>

Important Note

Row Level Security Constraints are applied at the MQL Layer.  The Business Columns referenced in the MQL Security Constraints will be resolved down to SQL Table Columns.  The Tables which contain column references included in security constraints will be joined to your query, based on the relationships defined in the Business Model.  It is recommended that you do not use outer joined business columns for the purposes of security constraints.