[
https://issues.jboss.org/browse/TEIID-5840?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5840:
---------------------------------------
There are two cases where someone may want the loosely coupled functionality:
- individually permission foreign temporary tables, which won't yet be defined in
metadata. The workaround would be to use a grant that specifies the catch all DATABASE
type, which then would not validate the target. If a table, procedure, schema, etc. are
specified we'll expect that it should be resolvable.
- with multi-schema import from a source to individually permission the "sub"
schemas:
teiidSchema."foreignSchema.tableName" - however with the change in TEIID-5841 we
won't make that check anymore as to prevent any ambiguity in resource names.
Add validation of grant / revoke targets
----------------------------------------
Key: TEIID-5840
URL:
https://issues.jboss.org/browse/TEIID-5840
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 13.0
We should be more pedantic about the targets of GRANT/REVOKE as they now specify both
object type and name. Currently a grant against a non-existent target will still succeed
- this is hold over from the loosely coupled permissioning model from designer.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)