db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3334) UserAuthenticator class needs to define its handling of user name more clearly.
Date Mon, 24 Jun 2013 23:30:22 GMT

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

Mamta A. Satoor commented on DERBY-3334:

Really old jira with no activity since it got created
> UserAuthenticator class needs to define its handling of user name more clearly.
> -------------------------------------------------------------------------------
>                 Key: DERBY-3334
>                 URL: https://issues.apache.org/jira/browse/DERBY-3334
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:,,,,,,,,,
>            Reporter: Daniel John Debrunner
>            Priority: Minor
> Java doc for UserAuthenticator class should clearly state the input format for user name.
> Currently the javadoc uses the terms "case-insensitive authorization identifier" and
"case-sensitive authorization identifier", which is incorrect. Authorization identifiers are
always case sensitive, it's their representation as user names that has the appearance of
being case insensitive.
> Note that user names are not really case sensitive or case insensitive, non-delimited
names are upper-cased to become an authorization identifier.
> This wiki page has the SQL rules that lead to this behaviour.
> http://wiki.apache.org/db-derby/UserIdentifiers

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message