Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com
 designates 209.85.212.50 as permitted sender)
MIME-Version: 1.0
Sender: ayyagarikiran@gmail.com
In-Reply-To: <4E206268.4020404@labeo.de>
References: 
 <CAJZgDFckLyOgfdv5tMZkLf-hs=wyXLK2yMJ0X8kmOYrZRptO+w@mail.gmail.com>
	<4E206268.4020404@labeo.de>
Date: Fri, 15 Jul 2011 22:38:25 +0530
Message-ID: 
 <CABzFU-cwOr+8Ccxq-h+t4VuWRhtswAzCcf1jnbTfcnx-VoTFpA@mail.gmail.com>
Subject: Re: ApacheDS Interceptor
From: Kiran Ayyagari <kayyagari@apache.org>
To: users@directory.apache.org
Content-Type: multipart/alternative; boundary=20cf307ca31898b5bc04a81eb2e2

--20cf307ca31898b5bc04a81eb2e2
Content-Type: text/plain; charset=ISO-8859-1

Hi Kevin,
    If you are using the version ,2.0-M1 then there exists a password
hashing interceptor enabled by defaut and there exists support for many
hashing algorithms, you just need to set the relevant implementation's FQCN.

Let us know if you still have issues with bind() after this change

On 15-Jul-2011 9:23 PM, "Stefan Zoerner" <stefan@labeo.de> wrote:

Hi Kevin,

currently I am quite busy and others at the users mailing list know the
server much better than me.

I therefore forward it to the list. Hopefully, you are subscribed to it.
Greetings from Hamburg,
   StefanZ

Am 15.07.2011 14:26, schrieb Kevin Hamilton:

> Sorry to bother you, but I just came across your interceptor tutorial
> for ApacheDS. Thank you for it! It has greatly helped me. I was able
> to successfully configure it. The problem I am facing is that I
> implemented my own custom hash into the interceptor rather than use
> the MD5. It works well and hashes the passwords whenever someone
> modifies or adds a new one.
>
> The problem I am having is that with my custom hash, the server does
> not know to hash the passwords on a bind attempt. I attempted to write
> a function that intercepted bind, but it did not work. I was wondering
> if you could give me some direction in this problem. I tried the code
> below to intercept the bind, but it did not work.
>
> public void bind(NextInterceptor next, BindOperationContext opContext)
>                throws Exception {
>                byte[] password = opContext.getCredentials();
>
>                if (password != null) {
>                        password = applyHashAlgorithm(**hashAlgorithm,
> password);
>                }
>
>                opContext.setCredentials(**password);
>
>                super.bind(next, opContext);
>                }
>
> If you have time, please give me some advice.
>
> Thanks,
> Kevin
>
>

--20cf307ca31898b5bc04a81eb2e2--