Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 32339 invoked from network); 21 May 2007 22:23:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 22:23:08 -0000 Received: (qmail 40989 invoked by uid 500); 21 May 2007 22:23:12 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 40957 invoked by uid 500); 21 May 2007 22:23:12 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 40946 invoked by uid 99); 21 May 2007 22:23:12 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 15:23:12 -0700 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=RCVD_NUMERIC_HELO,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of m96@gmx.li designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 21 May 2007 15:23:03 -0700 Received: (qmail invoked by alias); 21 May 2007 22:22:41 -0000 Received: from 201.231.76.83.cust.bluewin.ch (EHLO [192.168.11.11]) [83.76.231.201] by mail.gmx.net (mp017) with SMTP; 22 May 2007 00:22:41 +0200 X-Authenticated: #10527856 X-Provags-ID: V01U2FsdGVkX1/UzLAUBLjUsGwRPzRyr43L2w5Oi//G1yoOxeTLA0 W8E0hkqQWxiUSH Subject: Re: ERROR 58009: Network protocol exception From: m96 To: Derby Discussion In-Reply-To: <1179779732.8496.20.camel@localhost> References: <1179779732.8496.20.camel@localhost> Content-Type: text/plain Date: Tue, 22 May 2007 00:22:30 +0200 Message-Id: <1179786150.8496.31.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org ok, found the documentation page where it says that AuthorizationIdentifier's must comply [2] with SQL92Identifier [3] [4] syntax. so i need to reformulate my open question: is it possible to map user names. e.g. using 'user@host.com' for authentication which maps to 'user1' for authorization in db after successful authentication? and still what is DSS chain? thanks, cheers... [2] http://db.apache.org/derby/docs/dev/ref/rrefrauthid.html [3] http://db.apache.org/derby/docs/dev/ref/crefsqlj34834.html [4] http://db.apache.org/derby/docs/dev/ref/crefsqlj1003454.html On Mon, 2007-05-21 at 22:35 +0200, m96 wrote: > hi, > > I have written a new authentication Class that implements > UserAuthenticator according to [1] for my derby network server. but > unfortunately i get the following error: > > --- > ERROR 58009: Network protocol exception: DSS chained with same id at the > end of same id chain parse. The connection has been terminated. > ERROR 08004: Connection authentication failure occurred. Reason: the > user id is not authorized to access the database. > --- > > after some try-and-error i found out that this happens when the user > name is an email address (e.g. 'user@host.com') or begins with a number > (e.g. '123456'.) on the other hand user names like 'user' or 'user1' > work fine. > > the question that i have is: what is DSS chain and what does error 58809 > mean? additionally is there a user name convention - if yes, where is it > documented? > > furthermore if i can not user numbers only or special characters like > '@' in user names then is it possible to map user names. e.g. for > authentication i'm using 'user@host.com' and after successful > authentication it's mapped by my authentication class to an other name > 'user1' ? > > > thanks in advance. > cheers... > > > [1] http://db.apache.org/derby/docs/dev/devguide/rdevexudclass.html >