Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 60190 invoked from network); 18 Feb 2009 13:55:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Feb 2009 13:55:20 -0000 Received: (qmail 30944 invoked by uid 500); 18 Feb 2009 13:55:20 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 30747 invoked by uid 500); 18 Feb 2009 13:55:19 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 30738 invoked by uid 99); 18 Feb 2009 13:55:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2009 05:55:19 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [81.169.146.162] (HELO mo-p00-ob.rzone.de) (81.169.146.162) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Feb 2009 13:55:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1234965286; l=1652; s=domk; d=labeo.de; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Subject:To:MIME-Version:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH: DomainKey-Signature; bh=c74ORtRA6lnH85AMt36W+yADdj7kayLRIEO/Aj+Yyy4=; b=YL58bbOOk09k5Y0L4Kx76O4C3FcOj2jZfgee7NsUZkrLjSW3ugGHXJMfjpnPT+4d+06 PF8LNgo0DV+d8oI8rE+r9rI7+wpeTppz3KIVJ4Uz5/D9MUlEcXg/C8cu++BoQ7OhOG+mk Ia9KHy/l1Vjlc6vbV3NwyCpxs0LprAFyDJ0= DomainKey-Signature: a=rsa-sha256; s=domk; d=labeo.de; c=nofws; q=dns; h=X-RZG-AUTH:X-RZG-CLASS-ID:Date:From:MIME-Version:To:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Fd1FdFOKnObFUyMa2gUbDWydvbJG/dcnW+KYwgeb5p0gHBoca025KZoyCCTWKL5tb+0 l+iisnHlcgKFmXejIeNKUGHe0ZdZ+WYenDMAWiYA25ztYB2fltupRzr5VRfnbCGcNGpAV SZvKTMD4w7hKjdcbvnzc93ZmBuFck4W61FE= X-RZG-AUTH: :P3gBc0GmW/MphhhpU4BSj2bmx/Zwgz97J2mNwJqPNEXOKVIWxMhSD+tYA+j7nA== X-RZG-CLASS-ID: mo00 Received: from [127.0.0.1] ([145.253.187.146]) by post.strato.de (fruni mo2) (RZmta 18.18) with ESMTP id Z00a30l1IDgLF2 for ; Wed, 18 Feb 2009 14:54:46 +0100 (MET) Message-ID: <499C1328.9070201@labeo.de> Date: Wed, 18 Feb 2009 14:54:48 +0100 From: Stefan Zoerner User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: ApacheDs - DIGEST-MD5 References: <22076098.post@talk.nabble.com> <22076693.post@talk.nabble.com> <22077027.post@talk.nabble.com> <499C0093.9020806@labeo.de> <22078860.post@talk.nabble.com> In-Reply-To: <22078860.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Nowhere wrote: > thanks for you interesting... > I can't say what is my command line...I don't understand what you mean, > sorry :( > Perhaps you mean java command line? I use: java AdvancedBindDemo fullname > inClearText where fullname exists on my server. If I change my code from: > > ---> // Step 3: Bind with found DN and given password > ctx.addToEnvironment(Context.SECURITY_PRINCIPAL, dn); > ctx.addToEnvironment(Context.SECURITY_CREDENTIALS, password); > // Perform a lookup in order to force a bind operation with JNDI > ctx.lookup(dn); <------ > > TO: > > ---> // Step 3: Bind with found DN and given password > ctx.addToEnvironment(Context.SECURITY_PRINCIPAL, "fullname"); > ctx.addToEnvironment(Context.SECURITY_CREDENTIALS, password); > // Perform a lookup in order to force a bind operation with JNDI > ctx.lookup(dn); <--- > > Where I force cn I wish to use (and replace full dn) it works fine. With dn > I get the exception I said in previous post. Yes, thanks that was what I meant. I see much clearer now. > Anyway I can tell you it works for several users, yes... my problem is > getting it working with full dn and not only uid or cn...Sorry if I can't > explain it in a better way. > Thanks...any else question or help will be appreciated, Is the value of the fullname and the uid attribute of your users the same? I would it expect that it works with uid only; the CN is not necessarily unique. Why do you want to perform a search and use the DN, if you can use the unique uis immediatly? Do you plan to use another attribute for logon (like mail)? Greetings from Hamburg, Stefan