From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Steve Simon <steve@quintile.net>
References: <faaa980a2065101fa62467283fa420a1@quintile.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <faaa980a2065101fa62467283fa420a1@quintile.net>
Subject: Re: [9fans] authentication by LDAP?
Message-Id: <20060103011226.4BAC31E4137@dexter-peak.quanstro.net>
Date: Mon,  2 Jan 2006 19:12:26 -0600
Cc: 
Topicbox-Message-UUID: cd9dd48c-ead0-11e9-9d60-3106f5b1d025

is there anything about ldap that would prevent one from writing an
ldap adaptor for ndb? i was thinking something along these lines

	database=
		file=/lib/ndb/root
		dns=/srv/dns
		file=/lib/ndb/local
		file=/lib/ndb/common
		ldap=/srv/ldaps


ideally, the client could be oblivious to the source of the information.

fat chance, right?

- erik
	
"Steve Simon" <steve@quintile.net> writes

| 
| Currently there is no ldap client of any sort for plan9 (unless somone
| knows different?). I was looking at the RFCs again over chirstmas but
| once again I have recoiled from the complexity of it.
| 
| I imagine an ldap client which provides a number of interface
| directories, one of them which allows arbitary searches of the
| ldap database, and perhaps others which hold cached info in the
| form of flat files.
| 
| One of these flat files could be DNS info from LDAP in ndb(6) format
| which you could simply reference in /lib/ndb/local, e.g.
| 
| 	database=
| 		file=/lib/ndb/root
| 		file=/lib/ndb/local
| 		file=/lib/ndb/common
| 		file=/mnt/ldap/ndb
| 
| This is all very neat but vapourware at present - sorry, If I do get
| around to such a thing I will announce it here.
| 
| -Steve