[
https://issues.jboss.org/browse/TEIIDDES-2274?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-2274:
----------------------------------------
When in doubt please ask or see Teiid docs.
Both *Condition and Column Masking are available...
"condition" is a expression that is added on where clause, for ex: city =
'newyork', always accounts to a boolean expression
"Column Masking" is expression that is used instead of column value when the
above condition is satisfied. For example, this could be a string literal 'xxxxx'
or substring(2, column) or null. It needs to produce a value.
Note that the column(s) selected as part of the expression in the "condition"
has nothing to do with mask expression.
Row-based Security creates incorrect permission
-----------------------------------------------
Key: TEIIDDES-2274
URL:
https://issues.jboss.org/browse/TEIIDDES-2274
Project: Teiid Designer
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Modeling, VDB & Execution
Affects Versions: 8.3.3
Environment: OSX 10.9.4, Java 1.7.0_25. However, this bug has also been verified
on a RHEL 7 instance as well.
Reporter: Blaine Mincey
Assignee: Barry LaFond
Labels: designer, teiid
Fix For: 8.3.4, 8.6, 8.5.1
In modeling a VDB, when adding a condition for row-based security, an incorrect
permission is created. For example, if using the Designer to select a column, the
following condition is added:
<permission>
<resource-name>AccountsView.CUSTOMER.STATE</resource-name>
<condition constraint="true"><> 'New
York'</condition>
</permission>.
In order for row-based security to work, the VDB.xml needs to be edited to be the
following:
<permission>
<resource-name>AccountsView.CUSTOMER</resource-name>
<condition constraint="true">STATE <> 'New
York'</condition>
</permission>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)