[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: rewrite a login into a dn in simple bind

To: Ingo Schaefer <ingo@ingo-schaefer.de>
Subject: Re: rewrite a login into a dn in simple bind
From: Adam Williams <adam@morrison-ind.com>
Date: Mon, 13 Oct 2003 09:41:22 -0400
Cc: "OpenLDAP.org" <openldap-software@OpenLDAP.org>
In-reply-to: <1065653305.1114.21.camel@isch.fh-brandenburg.de>
References: <3F83DF4D.1070007@enatel.com> <20031008152554.3112318d.schaber@scan-plus.de> <Pine.GSO.4.58.0310080945270.21303@pula.ypass.net> <3F841695.8090004@enatel.com> <1065653305.1114.21.camel@isch.fh-brandenburg.de>

> You could avoid the configuration issue, if you save the dn of this
> group somewhere in a "special" place in the server - don't know, if the
> rootDSE is applicable for that. (But you have to configure your
> application anyway - at least the base-dn and the server name - so one
> more configuration option will be no problem.)

Just build your application to perform server location via SRV records. 
This is a standard, works very well, and SRV records are supported by
ever modern DNS server.  If you have M$ clients you probably have SRV
records already anyway (With AD they are created automatically).

References:
- rewrite a login into a dn in simple bind
  - From: Francois Beretti <francois.beretti@enatel.com>
- Re: rewrite a login into a dn in simple bind
  - From: Markus Schaber <schaber@scan-plus.de>
- Re: rewrite a login into a dn in simple bind
  - From: Igor Brezac <igor@ipass.net>
- Re: rewrite a login into a dn in simple bind
  - From: Francois Beretti <francois.beretti@enatel.com>
- Re: rewrite a login into a dn in simple bind
  - From: Ingo Schaefer <ingo@ingo-schaefer.de>

Prev by Date: Flexibility to have our home verify_callback while using TLS
Next by Date: Re: Postfix 2.0.16 CRAM/DIGEST-MD5 SMTP AUTH
Index(es):
- Chronological
- Thread