db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Orsini (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-866) BUILT-IN Derby User Management (DDL) Enhancements
Date Thu, 26 Jan 2006 01:00:09 GMT
    [ http://issues.apache.org/jira/browse/DERBY-866?page=comments#action_12364050 ] 

Francois Orsini commented on DERBY-866:

> Daniel John Debrunner commented on DERBY-866:
> ---------------------------------------------
> What's the purpose of returning the password column in the table/vti SYSUSERS?
Password won't be clearly readable, only the base64 representation of a already hashed password
- no risk really, just thought it could have some usage and if we use EXTERNAL to specify
that this user maps to one defined in some LDAP repository (as an example), then because of
EXTERNAL the password would not be encrypted and instead display the User DN ('uid=mary,ou=People,o=FlyTours.com')
that maps into LDAP...So in that case it would have a meaning...See my previous comment on
the EXTERNAL attribute definition. We could also decide not to display anything for built-in
stored passwords (eventhough they cannot be decrypted)...

> BUILT-IN Derby User Management (DDL) Enhancements
> -------------------------------------------------
>          Key: DERBY-866
>          URL: http://issues.apache.org/jira/browse/DERBY-866
>      Project: Derby
>         Type: Improvement
>   Components: Security
>     Versions:
>     Reporter: Francois Orsini
>      Fix For:
>  Attachments: Derby_User_Enhancement.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 contact one of the administrators:
For more information on JIRA, see:

View raw message