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] Resolved: (DERBY-3667) SQL roles: Make CURRENT_ROLE check that the role is still valid
Date Thu, 08 May 2008 11:39:56 GMT

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

Dag H. Wanvik resolved DERBY-3667.

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

Committed derby-3667-1 as svn 654482 and resolving.

> SQL roles: Make CURRENT_ROLE check that the role is still valid
> ---------------------------------------------------------------
>                 Key: DERBY-3667
>                 URL: https://issues.apache.org/jira/browse/DERBY-3667
>             Project: Derby
>          Issue Type: Task
>          Components: Security, SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>             Fix For:
>         Attachments: derby-3667-1.diff, derby-3667-1.stat
> When a role is the current role of a session, and that role is either
> a) revoked from current user or dropped, the present implementation
> does not actually reset the current role of value of the session which
> has set it to current, but instead lazily relies on the next usage to
> discover this fact by validating that the role usage is still
> applicable. This check is missing from CURRENT_USER.

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

View raw message