db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dag.Wan...@Sun.COM (Dag H. Wanvik)
Subject Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on shutting down Derby needs qualification
Date Tue, 29 Sep 2009 18:33:02 GMT
Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:

> "Francois Orsini (JIRA)" <jira@apache.org> writes:
>
>> If you have enabled Derby's BUILTIN user authentication and created
>> some user at the system level (for example, by setting some username
>> and password in the derby.properties file), you will need to specify
>> credentials (e.g. username and password) in order to shut down a
>> Derby system.
>
> So if I understand this correctly; if users are defined only on the
> database level (but BUILTIN user authentication is defined at the
> system level), it will still be possible to shut down a Derby system
> *without* supplying credentials?

Actually not. I tested this, and there needs to be defined at least
one user at the system level for a shutdown to work. So a more
precise wording would be:

"If you have enabled Derby's BUILTIN user authentication at the system
level (for example, by setting the property

      derby.connection.requireAuthentication=true 

in the derby.properties file), you will need to specify credentials
(e.g. username and password) in order to shut down a Derby system
*and* the supplied username/password must also be defined at the
system level."


Mime
View raw message