[jira] [Updated] (DERBY-866) Derby User Management Enhancements

["Rick Hillegas (Updated) (JIRA)" <ji...@apache.org>]

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

Rick Hillegas updated DERBY-866:
--------------------------------

    Attachment: UserManagement.html

Attaching a first version of a functional spec for NATIVE user management. This is an attempt to capture the discussion so far. Having a concrete proposal in front of us may help move the discussion forward. Your feedback is appreciated.

The following topics need more discussion:

1) This version of the spec does not address the issue of system-wide credentials. I will post a follow-on comment soon which tries to move that discussion forward.

2) This version of the spec phrases password procedure arguments as CLOBs in order to address the Java vulnerability described here: http://securesoftware.blogspot.com/2009/01/java-security-why-not-to-use-string.html An alternative approach would be to introduce a new Derby datatype corresponding to char[]. Other suggestions are welcome.

Thanks in advance for reading this spec.

                
> Derby User Management Enhancements
> ----------------------------------
>
>                 Key: DERBY-866
>                 URL: https://issues.apache.org/jira/browse/DERBY-866
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>    Affects Versions: 10.2.1.6
>            Reporter: Francois Orsini
>         Attachments: Derby_User_Enhancement.html, Derby_User_Enhancement_v1.1.html, UserManagement.html
>
>
> Proposal to enhance Derby's Built-In DDL User Management. (See proposal spec attached to the JIRA).
> Abstract:
> This feature aims at improving the way BUILT-IN users are managed in Derby by providing a more intuitive and familiar DDL interface. Currently (in 10.1.2.1), Built-In users can be defined at the system and/or database level. Users created at the system level can be defined via JVM or/and Derby system properties in the derby.properties file. Built-in users created at the database level are defined via a call to a Derby system procedure (SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY) which sets a database property.
> Defining a user at the system level is very convenient and practical during the development phase (EOD) of an application - However, the user's password is not encrypted and consequently appears in clear in the derby.properties file. Hence, for an application going into production, whether it is embedded or not, it is preferable to create users at the database level where the password is encrypted.
> There is no real ANSI SQL standard for managing users in SQL but by providing a more intuitive and known interface, it will ease Built-In User management at the database level as well as Derby's adoption.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira