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-3333) User name corresponding to authentication identifier PUBLIC must be rejected
Date Wed, 29 Oct 2008 12:33:44 GMT

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

Dag H. Wanvik commented on DERBY-3333:

Changed link to DERBY-2207 to "is related to", since the outstanding part of this issue is
not particular to roles,
but common to all grant/revoke functionality.

> User name corresponding to authentication identifier PUBLIC must be rejected
> ----------------------------------------------------------------------------
>                 Key: DERBY-3333
>                 URL: https://issues.apache.org/jira/browse/DERBY-3333
>             Project: Derby
>          Issue Type: Bug
>          Components: Security, SQL
>    Affects Versions:,,,,,,,,,
>            Reporter: Daniel John Debrunner
>             Fix For:
>         Attachments: DERBY-3333-roles.diff, DERBY-3333-roles.stat
> SQL Standard (foundation) says:
> Section 5.4 SR 20) No <authorization identifier> shall specify "PUBLIC".
> This is a syntax rule which implies a 42xxx SQL state but I wonder if 'invalid authorization
specification.' (28xxx) makes more sense?
> Maybe it's 28xxx when used in a connection request and 42xxx in a SQL statement?
> Needs to be disallowed on:
>   JDBC connection requests
>   GRANT statements, ie. using "PUBLIC" as a delimited identifier.
> Existing application impact if the exists a user with an authorization identifier of
PUBLIC in an existing system.

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

View raw message