You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <ji...@apache.org> on 2008/01/18 21:54:34 UTC

[jira] Created: (DERBY-3334) UserAuthenticator class needs to define its handling of user name more clearly.

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, Security
    Affects Versions: 10.3.2.1, 10.3.1.4, 10.2.2.0, 10.2.1.6, 10.1.3.1, 10.1.2.1, 10.1.1.0, 10.0.2.1, 10.0.2.0, 10.4.0.0
            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.
-
You can reply to this email to add a comment to the issue online.