From derby-dev-return-60401-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Mon Jun 02 12:00:10 2008 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 2678 invoked from network); 2 Jun 2008 12:00:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jun 2008 12:00:09 -0000 Received: (qmail 59103 invoked by uid 500); 2 Jun 2008 12:00:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 58876 invoked by uid 500); 2 Jun 2008 12:00:11 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 58865 invoked by uid 99); 2 Jun 2008 12:00:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 05:00:11 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 11:59:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 16B01234C12F for ; Mon, 2 Jun 2008 04:59:45 -0700 (PDT) Message-ID: <1114837414.1212407985091.JavaMail.jira@brutus> Date: Mon, 2 Jun 2008 04:59:45 -0700 (PDT) From: "Kristian Waagan (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601607#action_12601607 ] Kristian Waagan commented on DERBY-3327: ---------------------------------------- Regression tests on 10.4 ran without any failures: jars/sane/derby.jar] 10.4.1.4 - (661686M) suites.All: OK (10405 tests) derbyall: 100% Pass (274 tests passed) I'm considering committing the 5a patch to the 10.4 branch to resolve DERBY-3692. The other option is to pull out DERBY-3690. The code in patch 5a is extracted from 4e_full, and the only thing changed is the handling of the initial schema descriptor. > 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, derby-3327-5a-extracted_initial_schema_patch.diff, 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 part 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.