From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Steve Simon <steve@quintile.net>
Subject: Re: [9fans] authentication by LDAP?
Date: Mon, 2 Jan 2006 19:12:26 -0600 [thread overview]
Message-ID: <20060103011226.4BAC31E4137@dexter-peak.quanstro.net> (raw)
In-Reply-To: <faaa980a2065101fa62467283fa420a1@quintile.net>
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
next prev parent reply other threads:[~2006-01-03 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 22:32 Paweł Lasek
2006-01-02 12:35 ` Steve Simon
2006-01-03 1:12 ` erik quanstrom [this message]
2006-01-03 1:15 ` Russ Cox
2006-01-03 2:13 ` erik quanstrom
2006-01-03 2:34 ` Russ Cox
2006-01-03 2:53 ` erik quanstrom
2006-01-03 14:20 ` Paweł Lasek
2006-01-03 17:20 ` Dan Cross
2006-01-04 22:13 ` Paweł Lasek
2006-01-07 3:13 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060103011226.4BAC31E4137@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=steve@quintile.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).