db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-4551) Allow database user to execute stored procedures with same permissions as database owner and/or routine definer
Date Tue, 25 May 2010 13:58:26 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871150#action_12871150
] 

Dag H. Wanvik edited comment on DERBY-4551 at 5/25/10 9:57 AM:
---------------------------------------------------------------

Thanks for looking at the patch, Rick!

When a routine exits, any role set inside the routine will be popped back to whatever role
(or none) was set when the call was invoked. This is true whether definer's or invoker's rights
are used, as per the standard. 

In the implementation this is realized by popping the SQLSessionContext which was pushed at
call time. The "old" SQLSessionContext (the one which was active when the call was invoked)
is untouched during the invocation, and will still hold the "old" values of current user,
current role and current default schema at return time. 

The new thing with the patch is that the current user is also held by the stack of SQLSessionContexts,
making it possible to pop back from the defining user to the invoking user in a similar way
at return time.


      was (Author: dagw):
    Thanks for looking at the patch, Rick!

When a routine exists, any role set inside the routine will be popped back to whatever role
(or none) was set when the call was invoked. This is true whether definer's or invoker's rights
are used, as per the standard. 

In the implementation this is realized by popping the SQLSessionContext which was pushed at
call time. The "old" SQLSessionContext (the one which was active when the call was invoked)
is untouched during the invocation, and will still hold the "old" values of current user,
current role and current default schema at return time. 

The new thing with the patch is that the current user is also held by the stack of SQLSessionContexts,
making it possible to pop back from the defining user to the invoking user in a similar way
at return time.

  
> Allow database user to execute stored procedures with same permissions as database owner
and/or routine definer
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4551
>                 URL: https://issues.apache.org/jira/browse/DERBY-4551
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.5.3.0
>            Reporter: Tushar Kale
>            Assignee: Dag H. Wanvik
>         Attachments: definers_rights.html, definers_rights.html, definers_rights.html,
definers_rights.html, definers_rights.html, definers_rights.html, derby-4551-1.diff, derby-4551-1.stat,
derby-4551-1.txt
>
>
> Curretnly there is no way to hide data and database structure in embedded derby from
the end user. 
> One way to accomplish the above requirement is as follows:
> 1. Create encrypted database so data is protected
> 2. Enable authentication and sql authorization in database
> 3. Create two users, dbUser and dbOwner
> 4. Store application logic as stored procedure in the databse so dbUser does not know
what tables are accecced by the application logic, thus hiding table structure
> 5. Revoke select permission from dbUser so he cannot describe tables thus protecting
table structures
> 6. Give only Execute permissions on stored procedures to dbUser
> The above steps will ensure that data and data structure is hidden when application is
delivered to end user.
> The problem is, if user does not have select permission, the stored procedures will not
execute. So I am requesting the following enhancement to Derby:
> If dbOwner has given Execure permission to stored procecure to a dbUser, then allow stored
procedure to execute even if the dbUser has no select permission. 
> In otherwords, When dbUser calls stored procedure, database will use dbOwners authorization
to execute stored procedure rather than dbUsers.  
> This may be implemented by creating new permission called RunAsDbOwner.
> DbOwner can then grant permission to dbUser  to execute a stored procedure with RunAsDbOwner.
> If this is implemented, applications can be created which will truely hide the database
structure and data from end users. Database will behave as a blackbox with only in/out data
exposed in stored procedures.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message