Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Date: Tue, 29 Sep 2009 20:33:02 +0200
From: Dag.Wanvik@Sun.COM (Dag H. Wanvik)
Subject: Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on
 shutting down Derby needs qualification
In-reply-to: <x1oxd459zkd6.fsf@sun.com>
Sender: Dag.Wanvik@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x1ox8wfxzjmp.fsf@sun.com>
References: <1662151398.1253645655983.JavaMail.jira@brutus>
 <x1oxd459zkd6.fsf@sun.com>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.1 (usg-unix-v)

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."