[
https://jira.jboss.org/browse/TEIID-1231?page=com.atlassian.jira.plugin.s...
]
Steve Hawkins resolved TEIID-1231.
----------------------------------
Resolution: Done
Changed the code and the docs to note the difference in visibility. Also added handling
for the any-authenticated attribute.
Model visibility should only refer to whether entries are in
metadata
---------------------------------------------------------------------
Key: TEIID-1231
URL:
https://jira.jboss.org/browse/TEIID-1231
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 7.1.1
Reporter: Steve Hawkins
Assignee: Steve Hawkins
Fix For: 7.1.1
Visibility should only apply to whether a table/model shows up in the system tables and
should have nothing to do with whether it can be accessed.
If a designer user wants to make a model non-accessable with the ease of the visibility
mechansim, then they should create a data role ("default") that does not have
permissions for model. Our roles would then need a boolean attribute (any-authenticated)
to denote that any authenticated user has the role.
Designer/JOPR will also need to add support for the "any-authenticated"
attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira