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] Commented: (DERBY-2207) Improve usability of Derby's client/server security by implementing ANSI Roles
Date Tue, 29 Jan 2008 20:36:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563653#action_12563653
] 

Dag H. Wanvik commented on DERBY-2207:
--------------------------------------

As for the setting of NONE, please also see the discussion here: https://issues.apache.org/jira/browse/DERBY-3137?focusedCommentId=12540465#action_12540465
I think I agree that your reading is correct, but it seems restrictive..

I also notice that the corrigendum also now states in 18.3 (my emphasis):

"Set the *SQL-session role name* and the current role name for the current SQL-session context."

whereas previously it said:

"Set the current role name for the current SQL-session context."

Does this mean that the role set inside a stored procedure should be in effect also after
returning? Or is it just semantic
finery?

> Improve usability of Derby's client/server security by implementing ANSI Roles
> ------------------------------------------------------------------------------
>
>                 Key: DERBY-2207
>                 URL: https://issues.apache.org/jira/browse/DERBY-2207
>             Project: Derby
>          Issue Type: New Feature
>          Components: Security, SQL
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>         Attachments: spec.html, spec.html, spec.html, spec.html, spec.html, spec.html
>
>
> Implementing ANSI Roles will make it easier to manage security for multi-user applications
with high user turnover.

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