[
https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2761:
---------------------------------------
So in that case we could raise this above the data role level to VDB
property if that makes sense.
That's what I'm thinking. If left unspecified, then things will act as they do
today. If specified, then we'll require authentication into that security domain. As
a vdb property then it won't require invasive tooling changes. The only question
would be whether the security domain specified by the vdb has to also be specified in the
transport configuration.
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