db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-866) Derby User Management Enhancements
Date Wed, 28 Sep 2011 23:57:45 GMT

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

Dag H. Wanvik commented on DERBY-866:

Thanks for pushing this forward, Rick! Some questions and comments:

- q1: the password in the system table is the result of the hash, right? (not the password
- q2: salting?
- q3: should the system table be encrypted to avoid attacks? currently we encrypt entire database
which may not be what one wants(?)
- q4: boot-strap: how is the dbo user created? Autmatically when sing the provided connection
password when creating the database and seeing the property for the new scheme set in derby.authentication.provider?
- q5: database only properties is not default, but must be enabled. will the new mechanism
work without it? (cf. derby.database.propertiesOnly)
  If so, the authentication could be overridden by specifying another value for derby.authentication.provider.
- q6: do you see the scheme requiring SQL authorization enabled? If not, we'd need encryption
to avoid attacks: arbitrary user could backup entire database and stage dictionary attack
against the USER table...Btw, I forget, *is* backup restricted with authorization on? Docs
doesn't say...
- comment: creating a new user/role should cross-check each other to avoid collisions in uids.
- comment: the new feature only solves the issue of database level authentication, not system
level, obviously (limitation) 
> 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:
>            Reporter: Francois Orsini
>         Attachments: Derby_User_Enhancement.html, Derby_User_Enhancement_v1.1.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, 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


View raw message