db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3327) SQL roles: Implement authorization stack (and SQL session context to hold it)
Date Wed, 28 May 2008 11:03:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600434#action_12600434

Kristian Waagan commented on DERBY-3327:

Is it feasible to backport the last fix/commit to the 10.4 branch?
If not, I will pull out the fix for DERBY-3690 from 10.4 as it depends on this one.

I ran regression tests on 10.4 with the patch 'derby-3327-4-full-e.diff' applied, and the
only errors I got was in SQLSessionContextTest because roles are disabled. The errors happened
during setup, so I do now know yet if the tests pass if we enable roles again (for testing

> 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:
>         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.diff, DERBY-3327-4-full-e.stat, DERBY-3327-4-full.diff, DERBY-3327-4-full.stat,
> 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
> authorization identifers be pushed on a "authorization stack" when calling a stored procedure,
> SQL 2003, vol 2, section 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
> 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
> 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.

View raw message