Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1037767304.1212011565090.JavaMail.jira@brutus>
Date: Wed, 28 May 2008 14:52:45 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3327) SQL roles: Implement authorization
 stack (and SQL session context to hold it)
In-Reply-To: <8585052.1200590134098.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-3327:
---------------------------------

    Attachment: DERBY-3327-4-full-e-10_4.stat
                DERBY-3327-4-full-e-10_4.diff

Uploading a 10.4 version of this patch, DERBY-3327-4-full-e-10_4. The only difference
from DERBY-3327-4-full-e, is that the test is changed by commenting out the role test cases, since
roles is not a feature of 10.4. I verified that SQLSessionContextTest ran OK with the change on the
head of 10.4.

To your question, Kristian, I don't think there is a problem applying this to 10.4.

> SQL roles: Implement authorization stack (and SQL session context to hold it)
> -----------------------------------------------------------------------------
>
>                 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
>            Assignee: Dag H. Wanvik
>             Fix For: 10.5.0.0
>
>         Attachments: DERBY-3327-1.diff, DERBY-3327-1.stat, DERBY-3327-2.diff, DERBY-3327-2.stat, DERBY-3327-3.diff, DERBY-3327-3.stat, DERBY-3327-4-full-b.diff, DERBY-3327-4-full-b.stat, DERBY-3327-4-full-c.diff, DERBY-3327-4-full-c.stat, DERBY-3327-4-full-d.diff, DERBY-3327-4-full-d.stat, DERBY-3327-4-full-e-10_4.diff, DERBY-3327-4-full-e-10_4.stat, DERBY-3327-4-full-e.diff, DERBY-3327-4-full-e.stat, DERBY-3327-4-full.diff, DERBY-3327-4-full.stat, releaseNote.html
>
>
> 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 and 4.27.3 and 10.4 GR 5h and i.
> 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. 
> The authorization stack will be implemented as of the SQL session context.
> The patch will also implement the pushing of the current unqualified schema name part of
> the SQL session context, cf. 10.4 GR 5a (DERBY-1331).

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