W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 1999

how do we build custom realms

From: Zahid Ahmed <zahid.ahmed@commerceone.com>
Date: Fri, 21 May 1999 15:06:08 -0400 (EDT)
Message-ID: <DB7662837C64D211BBA600A0C9E91ABF53E78C@ip5->
To: Yves Lafon <ylafon@w3.org>
Cc: www-jigsaw@w3.org
A couple of question about realm support in

1. Is there a recommended way to do HTTP Basic 
Authentication scheme to do 1) password lookups
via LDAP? 2) password verificatoion via LDAP?

2. W.r.t. #1, how can we build a custom realm that can 
extend the authrealm and be configured programmatically
in the httpd during initialization? I want to configure
the custom realm via a different admin api than provided
by Jigsaw Admin. Looking at the realm and auth filter
apis, it seems that this is possible since all the
auth filter returns is a true/false or an ProtocolException
for authenticate().

Please provide guidelines about this.

thnx in advance.

> -----Original Message-----
> From: Zahid Ahmed 
> Sent: Tuesday, May 18, 1999 1:31 AM
> To: 'Benoit Mahe'; 'ylafon@w3.org'
> Subject: RE: Authentication extensions?
> Hi there,
> A couple of question about authentication support in Jigsaw.
> 1. How do we extend Jigsaw's HTTP Basic Authentication
>    with a similar speciailized basic authentication
>    that is integrated with LDAP. In other words, we want
>    to store the base64 encoded passwords in LDAP and
>    allow our custom http basic authentication component
>    to be used at connection time. How do we do that?
>    What classes to extend? What interfaces to implement?
Received on Friday, 21 May 1999 15:06:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:26 UTC