From derby-dev-return-73131-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue Sep 29 22:46:40 2009 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 87864 invoked from network); 29 Sep 2009 22:46:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Sep 2009 22:46:40 -0000 Received: (qmail 22958 invoked by uid 500); 29 Sep 2009 22:46:40 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 22896 invoked by uid 500); 29 Sep 2009 22:46:39 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 22888 invoked by uid 99); 29 Sep 2009 22:46:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 22:46:39 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of francois.orsini@gmail.com designates 209.85.222.198 as permitted sender) Received: from [209.85.222.198] (HELO mail-pz0-f198.google.com) (209.85.222.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2009 22:46:30 +0000 Received: by pzk36 with SMTP id 36so1522222pzk.5 for ; Tue, 29 Sep 2009 15:46:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=tqjU95v2FhCysRHLJVcteJG8J61/dMSDAh7s6RCEYCI=; b=aOiHNUOCKSJ458Dv9GRFxDiStHf6T7YMb1caShZQwX/5/Rsd9lkUZZABxi02GSY035 b5aJlLcPT5A4as0izlWDP7+foVnHa+Y6yg6KspEU1v7XEkRQuAX3QdPUNRRRUS5fU/IM hkYJnQ+IYB5pqc5Z5Ve6Rtr4ri4BveC3UmHlM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Q22/wUhhokdMqwN7HTperpWfrNFplCsXlqtanlbUH3TsLFxwAGHO3Tm8iiwbPiz6qc fN6RHWbCcspCVGKD09i2mkhf2A7KwYZ2ZH4CH9Xkh2S6DbLebzBVNaeoH1P9RhyF5VMu 7PJaKBmkfY/X9gqUELHIwqkUhk5lU1hRiWwwc= MIME-Version: 1.0 Received: by 10.115.149.10 with SMTP id b10mr9072270wao.157.1254264369115; Tue, 29 Sep 2009 15:46:09 -0700 (PDT) In-Reply-To: References: <1662151398.1253645655983.JavaMail.jira@brutus> Date: Tue, 29 Sep 2009 15:46:08 -0700 Message-ID: <7921d3e40909291546y4785022dh4d0d0552e07edf9b@mail.gmail.com> Subject: Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on shutting down Derby needs qualification From: Francois Orsini To: derby-dev@db.apache.org Content-Type: multipart/alternative; boundary=0016e646a2d22cf6180474bf2e4d X-Virus-Checked: Checked by ClamAV on apache.org --0016e646a2d22cf6180474bf2e4d Content-Type: text/plain; charset=ISO-8859-1 On Tue, Sep 29, 2009 at 11:17 AM, Dag H. Wanvik wrote: > "Francois Orsini (JIRA)" 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? > Nope - that is not what was meant. On the contrary, if you enable authentication at the system level and don't have any users created in derby.properties, you won't be able to shutdown a Derby instance at all via 'jdbc:derby:;shutdown=true' (besides exiting or/and killing the VM process). Users' credentials defined as part of a database are not involved when shutting down a Derby instance (not a database). --0016e646a2d22cf6180474bf2e4d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Sep 29, 2009 at 11:17 AM, Dag H. Wan= vik <Dag.Wanvik@= sun.com> wrote:
"Francois Orsini (JIRA)" <jira@apache.org> writes:

> If you have enabled Derby's BUILTIN user authentication and create= d
> 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?

Nope - that is no= t what was meant.

On the contrary, if you enable authentication at t= he system level and don't have any users created in derby.properties, you won't be able to shutdown a Derby instance at all via 'jdbc:derby:;shutdown=3Dtrue' (besides ex= iting or/and killing the VM process). Users' credentials defined as part of a= database are not involved when shutting down a Derby instance (not a datab= ase).

=A0

--0016e646a2d22cf6180474bf2e4d--