[
https://issues.jboss.org/browse/TEIIDDES-1480?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-1480:
------------------------------------------
the allowed-languages vdb property should just be a single comma separated property.
So what is the scope of the permission?
The allowed-languages vdb property enables the use of the given languages in the vdb.
Since this feature has a lot of room for abuse we want vdb designers to be specific about
what they are allowing. If data roles are in use, then just like with data access, you
are denied by default the ability to use those languages and must add a permission that
grants usage.
Can each role have only one permission defined for each
allowed-language ?
It doesn't really matter, the logic will simply accumulate the effects of each
permission in order, so in practical terms the last on wins.
Does that mean that there is no connection between
"allowed-language* and a model resource?
Yes there is no connection. If you are defining a view or procedure that language usage
is not checked against the permissions anyway - since these style of authorizations affect
the user query only.
Can these allowed-languages be defined separately in a list, and then
displayed and added/removed as permissions for each Role?
I'm not sure what you mean by separately in a list. But yes they can be granted on
each Role.
Add handling for language support in vdbs
-----------------------------------------
Key: TEIIDDES-1480
URL:
https://issues.jboss.org/browse/TEIIDDES-1480
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration
Reporter: Steven Hawkins
Assignee: Dan Florian
Fix For: 8.2
Teiid 8.2 added support for an OBJECTTABLE table function TEIID-2141. To use the
OBJECTTABLE construct, a vdb property allowed-languages and if applicable the data role
language permission needs granted. See the reference
https://docs.jboss.org/author/display/TEIID/XML+Definition for an example.
--
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