[ https://issues.jboss.org/browse/TEIID-2327?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2327: --------------------------------------- There are two approaches to take: 1. use a new metadata representation: <mask resource-name="">...</mask> ... such that resource-name must be a fully qualified column name (although it would make more sense to use schema/object/column). This would be defined separately from data roles as there is only a single masking definition that is applicable to a given column. The expectation would be that the masking expression would be a case statement based upon hasRole. or 2. add an ordered mask element to the permission metadata: <mask order="1">...</mask> Here we would determine the relevant mask by looking over all applicable roles for the mask with the lowest ordering. I'm leaning toward the second representation as it makes masking well coupled with the role definition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira