[
https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
There are a couple of considerations here. The first is whether it would be sufficient to
control this at a vdb level, rather than something at a low level. The next is that
REST/Web services due to the requirement of extension metadata are enabled specifically
for web consumption. Not exposing the end point procedures to other callers doesn't
seem like a major issue. The final thought is whether this should be tied into the
existing data roles mechanism (which it would probably need to be if control is down to
the procedure level). In theory the reason that access should vary by transport is that
there should be different security domains / roles in effect. The notion of an any
authenticated role could be extended to any authenticated in the following security
domains.
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
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