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] Created: (DERBY-3327) SQL roles: Implement authorization stack
Date Thu, 17 Jan 2008 17:15:34 GMT
SQL roles: Implement authorization stack
----------------------------------------

                 Key: DERBY-3327
                 URL: https://issues.apache.org/jira/browse/DERBY-3327
             Project: Derby
          Issue Type: New Feature
          Components: Security, SQL
            Reporter: Dag H. Wanvik
             Fix For: 10.4.0.0


The current LanguageConnectionContext keeps the user authorization identifier for an SQL session.
The lcc is shared context also for nested connections (opened from stored procedures).
So far, for roles, the current role has been stored in the lcc also. However, SQL requires
that
authorization identifers be pushed on a "authorization stack" when calling a stored procedure,
cf.
SQL 2003, vol 2, section 4.34.1.1. 
This allows a caller to keep its current role after a call even if changed by the stored procedure.

This issue will implement the current role name part ("cell") of the authorization stack.


-- 
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