[
https://issues.jboss.org/browse/TEIID-2761?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2761:
-------------------------------------
Right now VDB and security-domain are not related. So, if we restrict VDB to single
security-domain, that will restrict to the transport(s) that is configured with. [thinking
out loud]
Isn't more typical that each vdb will be in a single security
domain?
Yes, especially if they want to use data roles. It seems silly to have two
sets of users that authenticate differently for a given resource.
Generally wasn't the purpose of allowing multiple security domains
per transport so that different vdbs could >effectively be in different security
domains?
This was not the original intention, but I agree that fits the model. I
believe before we made a switch to JAAS, the requirement was to use different security
domains so that user could be authenticated with different security stores. In the JBoss
security-domain configuration, it gives that ability to configure multiple stores inside
single security-domain so that is satisfied.
So in that case we could raise this above the data role level to VDB property if that
makes sense.
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