Private schema not working correctly when owned by a role

Bug #1401678 reported by Paul Low
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trafodion
Fix Released
High
Cliff Gray

Bug Description

User is granted role.
Private schema is created with role as owner.
User is able to create table, but unable to create view and a weird error is returned.
User is also unable to drop the table that he created.
User is also unable to drop schema where role is the owner.

SQL>create role role1;

--- SQL operation complete.

SQL>grant role role1 to USERNAME1;

--- SQL operation complete.

SQL>create schema authorization role1;

--- SQL operation complete.

SQL>connect USERNAME1/PASSWORD1
Connected to Trafodion

SQL>set schema role1;

--- SQL operation complete.

SQL>create table tab1(a int);

--- SQL operation complete.

SQL>create view view1 as select * from tab1;

*** ERROR[1340] ROLE1 is not a user.
*** ERROR[20235] Error returned while converting user ID to username, status: 11 userid: 1000001.

SQL>drop table tab1;

*** ERROR[1017] You are not authorized to perform this operation.

SQL>drop schema role1 cascade;

*** ERROR[1017] You are not authorized to perform this operation.

SQL>

Tags: sql-security
Revision history for this message
Cliff Gray (cliff-gray) wrote :

This fix has been committed.

Changed in trafodion:
status: New → Fix Committed
Paul Low (paul-low-x)
Changed in trafodion:
milestone: none → r1.0
Paul Low (paul-low-x)
Changed in trafodion:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.