Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 29 Feb 2012 17:27:58 +0000 (UTC)
From: "Rick Hillegas (Updated) (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2023396269.3646.1330536478819.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-866) Derby User Management Enhancements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

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

    Attachment: derby-866-20-ab-npeAndUserProbing.diff

Tests passed cleanly for me. Attaching derby-866-20-ab-npeAndUserProbing.di=
ff. This version uses AuthenticationServiceBase.getDatabaseProperties() as =
Knut suggested. Committed at subversion revision 1295189.

               =20
> 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
>            Assignee: Rick Hillegas
>         Attachments: Derby_User_Enhancement.html, Derby_User_Enhancement_=
v1.1.html, DummyAuthenticator.java, UserManagement.html, UserManagement.htm=
l, UserManagement.html, UserManagement.html, UserManagement.html, UserManag=
ement.html, derby-866-01-aa-sysusers.diff, derby-866-01-ab-sysusers.diff, d=
erby-866-02-ag-createDropUser.diff, derby-866-03-aa-resetModifyPassword.dif=
f, derby-866-03-ab-resetModifyPassword.diff, derby-866-04-aa-fixRolesTest.d=
iff, derby-866-05-aa-grantRevoke.diff, derby-866-06-aa-upgradeFrom10.1.diff=
, derby-866-07-aa-removeSQLPassword.diff, derby-866-08-aa-passwordHasher.di=
ff, derby-866-08-ab-passwordHasher.diff, derby-866-08-ad-passwordHasher.dif=
f, derby-866-09-ad-nativeAuthenticationService.diff, derby-866-09-ae-native=
AuthenticationServiceWithTests.diff, derby-866-10-ac-propChanging.diff, der=
by-866-11-aa-upgradeTest.diff, derby-866-12-ac-passwordExpiration.diff, der=
by-866-13-ab-systemWideOperationTests.diff, derby-866-14-ac-badNativeSpec.d=
iff, derby-866-15-ae-dbInJarFileOrOnClasspath.diff, derby-866-16-aa-credDBV=
iaSubprotocol.diff, derby-866-17-aa-grantRevokeNative.diff, derby-866-18-aa=
-encryptedCredentialsDB.diff, derby-866-19-aa-replicationTest.diff, derby-8=
66-20-aa-npeAndUserProbing.diff, derby-866-20-ab-npeAndUserProbing.diff, du=
mmyCredentials.properties
>
>
> Proposal to enhance Derby's Built-In DDL User Management. (See proposal s=
pec attached to the JIRA).
> Abstract:
> This feature aims at improving the way BUILT-IN users are managed in Derb=
y by providing a more intuitive and familiar DDL interface. Currently (in 1=
0.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 sys=
tem 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_UT=
IL.SYSCS_SET_DATABASE_PROPERTY) which sets a database property.
> Defining a user at the system level is very convenient and practical duri=
ng the development phase (EOD) of an application - However, the user's pass=
word is not encrypted and consequently appears in clear in the derby.proper=
ties file. Hence, for an application going into production, whether it is e=
mbedded or not, it is preferable to create users at the database level wher=
e the password is encrypted.
> There is no real ANSI SQL standard for managing users in SQL but by provi=
ding a more intuitive and known interface, it will ease Built-In User manag=
ement 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira