db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-866) Derby User Management Enhancements
Date Mon, 28 Nov 2011 16:31:40 GMT

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

Rick Hillegas commented on DERBY-866:

Thanks for your comments, Bryan. I apologize for my scattershot series of questions and proposals.

I seem to have come to focus on the following problem: Provide an out-of-the-box authentication
scheme for Derby which is better than the current BUILTIN scheme. The new scheme would be
used by multi-user applications.

It doesn't matter whether the applications use Derby's Network Server framework or whether
they simply embed Derby inside their own session manager. The primary use of this scheme would
be to restrict access to databases, that is, to enforce a notion of database-specific user

The problem I was wrestling with in my last tranche of comments was this: Derby's other authentication
schemes are all JVM-wide schemes, not database-specific schemes. This lets them handle a couple
authentication problems which arise when you don't have a database. I am trying to figure
out how we want to handle these problems when application(s) want to use the new scheme across
all databases managed by a JVM.

It's true, I am striking out in many different directions all at once. I am trying to make
sure that the new scheme can handle all use-cases which the other schemes do today. This involves
making sure that it will fit into candidate solutions for problems which we haven't addressed
yet, like the database restoration problem described by DERBY-2470.

> 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