[
https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
grant-all should be handled as an attribute on a role. I'm not sure what the handling
should be for the all in security domain. Seems like it will require a new collection on
the data role. Another consideration is to have the role name mapping mechanism use a
full form of role-name\@security-domain (similar to how we approach making user names
specific to a security domain). Currently we don't specify what security domain a
given mapped role is from, but it seems like this is probably a good idea in general. We
could then just allow the role mapping \@security-domain to mean map to any user from that
security domain.
Enable/disable transport per model/view/virtual procedure
---------------------------------------------------------
Key: TEIID-2761
URL:
https://issues.jboss.org/browse/TEIID-2761
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.5
Reporter: Patrick Deenen
Assignee: Steven Hawkins
Fix For: 8.7
It would be nice to be able to enable and disable access to models, tables, views or
(virtual) procedures for a specific transport (JDBC, ODBC, OData, REST, Web services).
One may want to have access to virtual procedures only by Odata for 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