[
https://issues.jboss.org/browse/TEIID-2695?page=com.atlassian.jira.plugin...
]
Van Halbert commented on TEIID-2695:
------------------------------------
If in procedure, I need to do conditioning logic based on if this person is part of a
group (say accounting vs hr). Basically, anywhere I need to check the role before doing
something.
You can't have a role defined in vdb.xml and not JAAS, and still give permission, can
you? Therefore, wouldn't it be better to just use what defined in JAAS, and not worry
about the vdb.xml, cause it all has to be in JAAS anyway to work
Unable to use CASE statement in Select
--------------------------------------
Key: TEIID-2695
URL:
https://issues.jboss.org/browse/TEIID-2695
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.4.1
Reporter: Van Halbert
Assignee: Steven Hawkins
Attachments: portfolio-vdb.xml
Trying to add a <mask> of:
<permission>
<resource-name>Stocks.StockPrices.Price</resource-name>
<mask>CASE WHEN hasRole('prices') THEN Price END</mask>
</permission>
even tried using "= true" just to see
but it it always returns null for Prices.
To test it, I logged in as 'user' using CommandLog vdb and issued:
Select VDB, CASE WHEN hasRole('prices') THEN 'Y' Else 'N' END as
V from TEIID_COMMANDLOG
and 'N' was always returned for column V.
teiid roles file:
# A roles.properties file for use with the UsersRolesLoginModule
# username=role1,role2
portfolio=superuser
viewonly=readonly
user=user,prices
--
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