[
https://issues.jboss.org/browse/TEIID-5792?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5792:
---------------------------------------
we should wrap the call in select to specify cols which we want to
request
Which is logically creating a view, thus the expectation of the suggested workaround in
this case.
For views if we use "select *" and have restrictions on
columns we will get error until we specify allowed columns.
With the org.teiid.ignoreUnauthorizedAsterisk option, you can still use select *
Permissions don't work with virtual procedures' ResultSet
---------------------------------------------------------
Key: TEIID-5792
URL:
https://issues.jboss.org/browse/TEIID-5792
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Affects Versions: 12.0
Environment: teiid-12.0.0 on WildFly Full 14.0.1.Final (WildFly Core
6.0.2.Final)
Reporter: Dmitrii Pogorelov
Assignee: Steven Hawkins
Priority: Major
Teiid doesn't work with ResultSet of a virtual procedure. For example, if we have
procs.testProc virtual procedure which can return two values in ResultSet: a and b and we
specify a permission for one of these columns in ResultSet, the permission won't
work:
{code:xml}
<permission>
<resource-name>procs.testProc.a</resource-name>
<allow-read>false</allow-read>
</permission>
{code}
I think it would be great to set permissions also for ResultSets of virtual procedures,
so AuthorizationValidationVisitor.validateEntitlements method for a GroupSymbol, which is
a procedure, should analyze also its ResultSet. At the same time permissions work for
virtual views and we can set permissions for some views' columns separately.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)