[
https://issues.jboss.org/browse/TEIIDDES-2274?page=com.atlassian.jira.plu...
]
Ramesh Reddy commented on TEIIDDES-2274:
----------------------------------------
[
https://docs.jboss.org/author/display/TEIID/XML+Definition] there are two separate
examples one for row filtering (or row based security), one for the masking. I am not sure
where the confusing part is, the above text is from row based security, the xml example is
from masking.
If you re-read my comment above, expression used in the condition is independent from the
*resource* column/table. There is no restriction that it has to use same column. What
document is saying is when condition is used, the expression must be able to evaluated
against the parent table/view. Obviously you not can enter a Condition that uses table
Y's columns, when you are defining a row filter or mask column on table X.
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)