Bug 780903 (SOA-3366) - hasROLE(rolename) function always returns false
Summary: hasROLE(rolename) function always returns false
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3366
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Documentation, EDS
Version: 5.2.0.ER3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.3.0 GA
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-08 19:46 UTC by Paul Nittel
Modified: 2011-11-15 18:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Fedora 14, SOA-P 5.2 ER3
Last Closed: 2011-11-15 18:31:13 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3366 0 None None None Never

Description Paul Nittel 2011-09-08 19:46:49 UTC 
project_key: SOA

Given teiid-security-roles.properties contains user=NoRolesRole and the VDB in use has data roles defined, when logged into Teiid as user, the following SQL should return true.

SELECT hasROLE('NoRolesRole')

However, it always--AFAICT--returns false.

(Roles are working for this VDB as this user is not able to query certain tables.)
Comment 1 Van Halbert 2011-09-08 19:46:50 UTC 
Link: Added: This issue Cloned from TEIID-1747
Comment 2 Van Halbert 2011-09-08 19:47:13 UTC 
Security: Added: Public
Comment 3 Van Halbert 2011-09-08 20:49:10 UTC 
The problem is that the jaas role name was used, not the teiid data role name, in the function.   The documentation will be updated to clarify this.
Comment 4 Van Halbert 2011-09-12 17:32:32 UTC 
Teiid committed the doc change: Revision: 3461

to the 7.4.x branch.
Comment 5 David Le Sage 2011-09-21 03:13:15 UTC 
Release Notes Docs Status: Added: Not Required
Writer: Added: dlesage
Comment 6 Van Halbert 2011-11-14 14:01:17 UTC 
Teiid committed the documentation fix.  This clarification should make its way into the 5.3 release.
Comment 7 Paul Nittel 2011-11-15 18:31:13 UTC 
The software does, in fact, work properly. Doc will be fixed for 5.3. Closed.
Note You need to log in before you can comment on or make changes to this bug.