The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] YP / NIS / NIS+ / LDAP
Date: Mon, 5 Nov 2018 15:53:12 -0700	[thread overview]
Message-ID: <121753c0-ad8b-428f-498b-002749baf132@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1811060645430.78183@aneurin.horsfall.org>

[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]

On 11/05/2018 12:58 PM, Dave Horsfall wrote:
> I've used OpenLDAP in a previous job for many years, for all sorts of 
> things, and it worked well.  I had it integrated with Sendmail and even 
> Kerberos, but I've forgotten the details now.

ACK

My biggest problem with OpenLDAP, or any LDAP, is (other than my 
ignorance) the fact that all of them (save for AD) started with an empty 
schema.  So I was functionally needing to create a schema that was 
hopefully compatible with the things I needed /while/ learning LDAP ~> 
$LDAPimplementation.  I always felt it was a relatively steep learning 
curve.  And I was never sufficiently motivated.

Conversely, AD, has a very well established LDAP schema and many things 
know how to work with it.

> There is a damned good book on LDAP in general (I can't remember the 
> title, but it's a thick hard-cover)

Do you by chance know any more details?  I'll dig and see if I can find it.

> so read it, cover to cover.  Then download the OpenLDAP source (or used 
> a trusted binary) and read the documentation, esp. the quick start guide 
> and the admin guide.

ACK

> Then read them again :-)

~chuckle~

> The most important thing about learning LDAP is forgetting everything 
> you ever knew about relational databases; LDAP is a *directory*, not a 
> database, and the idiots at work were constantly referring to records, 
> not *entries*, which drove me crazy (I have a Unify RDBMS background too).

I think I understand that.  Or at least what (little) I know doesn't 
doesn't seem to have any objection to that.  I know that I would not 
want to use LDAP as a general purpose relational database.

> And if/when you start using OpenLDAP, always keep it up to date; there 
> is an active mailing list, but the first thing they'll ask is "What 
> version are you running?".  Sure, there's been some lemon releases, but 
> in general it worked fine for us; the company's balls depended upon it.

Thank you for the ProTip.



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3982 bytes --]

  reply	other threads:[~2018-11-06  0:32 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04 20:51 Grant Taylor via TUHS
2018-11-04 21:46 ` Ben Greenfield via TUHS
2018-11-04 22:45 ` Arthur Krewat
2018-11-04 22:58 ` Mantas Mikulėnas
2018-11-04 23:49   ` Warner Losh
2018-11-05  3:16 ` Robert Brockway
2018-11-05  6:08   ` Grant Taylor via TUHS
2018-11-05  7:24     ` Mantas Mikulėnas
2018-11-05  7:33       ` Mantas Mikulėnas
2018-11-05 16:12       ` Arthur Krewat
2018-11-05 19:32         ` Grant Taylor via TUHS
2018-11-05 22:43           ` Arthur Krewat
2018-11-06  5:25             ` Grant Taylor via TUHS
2018-11-06 16:50               ` Arthur Krewat
2018-11-06 19:43                 ` Grant Taylor via TUHS
2018-11-05 19:27       ` Grant Taylor via TUHS
2018-11-05 19:36       ` Grant Taylor via TUHS
2018-11-05 21:36         ` Mantas Mikulėnas
2018-11-05 23:12           ` Grant Taylor via TUHS
2018-11-05 21:43         ` Ben Greenfield via TUHS
2018-11-06  4:58           ` Grant Taylor via TUHS
2018-11-06 12:59             ` Ben Greenfield via TUHS
2018-11-06  6:53           ` Mantas Mikulėnas
2018-11-06 13:21             ` Ben Greenfield via TUHS
2018-11-06 13:44               ` Mantas Mikulėnas
2018-11-06 14:00                 ` Ben Greenfield via TUHS
2018-11-06 13:46               ` Mantas Mikulėnas
2018-11-05 22:34         ` Dan Cross
2018-11-06  5:24           ` Grant Taylor via TUHS
2018-11-06  7:07             ` Mantas Mikulėnas
2018-11-06 17:30               ` Grant Taylor via TUHS
2018-11-06 19:58                 ` Mantas Mikulėnas
2018-11-06 22:24             ` Dan Cross
2018-11-07  0:35               ` Grant Taylor via TUHS
2018-11-07 11:37                 ` Pete Turnbull
2018-11-07 17:30                   ` Grant Taylor via TUHS
2018-11-07 22:01                     ` Dave Horsfall
2018-11-08  1:48                       ` Dave Horsfall
2018-11-07 23:00                     ` Pete Turnbull
2018-11-07  1:03             ` Pete Turnbull
2018-11-06 12:54           ` Ben Greenfield via TUHS
2018-11-05 20:10     ` Dave Horsfall
2018-11-05  3:49 ` Larry McVoy
2018-11-05  6:12   ` Grant Taylor via TUHS
2018-11-05 19:58     ` Dave Horsfall
2018-11-05 22:53       ` Grant Taylor via TUHS [this message]
2018-11-06  1:28         ` Dave Horsfall
2018-11-05 15:44   ` Larry McVoy
2018-11-05 18:38     ` arnold
2018-11-05 19:04       ` Larry McVoy
2018-11-05 21:21         ` Noel Hunt
2018-11-07  8:58         ` arnold
2018-11-07 14:05           ` arnold
2018-11-05 20:48 ` A. P. Garcia
2018-11-05 23:07   ` Grant Taylor via TUHS
2018-11-06  1:46     ` Dan Cross
2018-11-06  5:32       ` Grant Taylor via TUHS
2018-11-06 22:29         ` Dan Cross
2018-11-07  0:40           ` Grant Taylor via TUHS
2018-11-07  1:38           ` Arthur Krewat
2018-11-06  3:03     ` Robert Brockway
2018-11-06  5:03       ` David Arnold
2018-11-06  5:34       ` Grant Taylor via TUHS
2018-11-06 23:59 Norman Wilson

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=121753c0-ad8b-428f-498b-002749baf132@spamtrap.tnetconsulting.net \
    --to=tuhs@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.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).