Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <435A9AE2.7020204@debrunners.com>
Date: Sat, 22 Oct 2005 13:02:42 -0700
From: Daniel John Debrunner <djd@debrunners.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: SQL Exception: Connection refused : Invalid authentication.
References: <op.syz354vcp1z4zz@komhem>
 <58ed70f50510210833r1f9f1585m1060ab190aa97037@mail.gmail.com>
 <op.sy19mkw2p1z4zz@localhost> <435A8FA2.4040606@debrunners.com>
 <op.sy2ca4m0p1z4zz@localhost>
In-Reply-To: <op.sy2ca4m0p1z4zz@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Arne Anka wrote:

>> You use SYSCS_SET_DATABASE_PROPERTY to define the user in the database
>> for the builtin authentication scheme. Eg.
>>
>> SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY('derby.user.arne','cat76dog')");
>>
>>
>> Then when you connect to derby you pass in the user name and password
>> values using the property keys 'user' and 'password'. This is because
>> user/password is the standard as defined by JDBC.
>>
>> E.g.
>>
>> prop.setProperty("user", "arne");
>> prop.setProperty("password", "cat76dog");
> 
> 
> sounds good (and obvious ;-). have to test monday when i'm back in office.
> but it's not really clear to me why it works the first time. after all,
> to  read from my db a acquire a new connection with the
> properties-object ...
>

I think it's because with the first connection, a newly created
database, there is no authentication enabled so Derby allows any
connection request to succeed, even those where a user name is not supplied.

Dan.