Hi Guys, I am just wanting to centralise all my users across a couple of
systems to the 1 database replicated across all the machines. I know
traditionally LDAP has been the thing to use for this but no matter how hard
I try I can't get my head around exactly how LDAP stores information. I have
got it working and I've been using it for a while now but I find it not so
easy to administer.

If I were to use MySQL it would be as simple as using phpmyadmin plus custom
PHP scripts I could write to do certain things for me. I have seen pam-mysql
& libnss-mysql packages, will this do everything LDAP can do and is it as
secure and reliable or is it more of an afterthought/hack-around?

On Oct 9, 1:37 am, "Michael Everson" <s...@qeidrafting.com> wrote:
> Hi Guys, I am just wanting to centralise all my users across a couple of
> systems to the 1 database replicated across all the machines. I know
> traditionally LDAP has been the thing to use for this but no matter how hard
> I try I can't get my head around exactly how LDAP stores information. I have
> got it working and I've been using it for a while now but I find it not so
> easy to administer.
>
> If I were to use MySQL it would be as simple as using phpmyadmin plus custom
> PHP scripts I could write to do certain things for me. I have seen pam-mysql
> & libnss-mysql packages, will this do everything LDAP can do and is it as
> secure and reliable or is it more of an afterthought/hack-around?

Yes, it will do everything that LDAP can do. Everything but offer the
functionality of LDAP, that is.

LDAP isn't a database, it is a communications protocol. It is a way
for a client application to ask for and receive "telephone book"
information about people or departments. It involves a specific
structure in it's request and in the reply. /That/ is LDAP
("Lightweight Directory Access Protocol").

You can build an alternative to LDAP out of MYSQL and PHP, but it
won't substitute for LDAP. LDAP clients need to talk LDAP to an LDAP
server. They won't talk your custom language to your custom server,
unless you build your custom server to talk LDAP.

In the end, you aren't really looking for a PHP/MYSQL alternative to
LDAP. Instead, you are looking for an easily administered LDAP server.
So, look for one, say, in Freshmeat or sourceforge. In fact, I'll help
a bit - take a look at http://diradmin.open-it.org/

HTH
--
Lew

In <dsEOi.7235$H22.4584@news-server.bigpond.net.au>,
"Michael Everson" <spam@qeidrafting.com> mentions:
>Hi Guys, I am just wanting to centralise all my users across a couple of
>systems to the 1 database replicated across all the machines. I know
>traditionally LDAP has been the thing to use for this but no matter how hard
>I try I can't get my head around exactly how LDAP stores information. I have
>got it working and I've been using it for a while now but I find it not so
>easy to administer.
>
>If I were to use MySQL it would be as simple as using phpmyadmin plus custom
>PHP scripts I could write to do certain things for me. I have seen pam-mysql
>& libnss-mysql packages, will this do everything LDAP can do and is it as
>secure and reliable or is it more of an afterthought/hack-around?

I believe there is a "mysql" back-end to openldap. (might be postgresql though)

IMO.. I wish postgresql would be more popular, as it really is a better
database. :-P

No, seriously, the problem is, LDAP is a protocol offering directory services,
optimized for "read-mostly" data, the kind of thing you're likely to find
in a phone book, DNS server or.. user account.

I know it's a confusing mess, but it could be worse, you could be forced
to use SOAP.

Jamie
--
http://www.geniegate.com Custom web programming
Perl * Java * UNIX User Management Solutions

A mysql backend to LDAP might be ok
What's the normal backend for LDAP storage then, is it just a db text file
or something?



"Jamie" <nospam@geniegate.com> wrote in message
news:Lc119300731754990x1333b50@saturn...
> In <dsEOi.7235$H22.4584@news-server.bigpond.net.au>,
> "Michael Everson" <spam@qeidrafting.com> mentions:
>>Hi Guys, I am just wanting to centralise all my users across a couple of
>>systems to the 1 database replicated across all the machines. I know
>>traditionally LDAP has been the thing to use for this but no matter how
>>hard
>>I try I can't get my head around exactly how LDAP stores information. I
>>have
>>got it working and I've been using it for a while now but I find it not so
>>easy to administer.
>>
>>If I were to use MySQL it would be as simple as using phpmyadmin plus
>>custom
>>PHP scripts I could write to do certain things for me. I have seen
>>pam-mysql
>>& libnss-mysql packages, will this do everything LDAP can do and is it as
>>secure and reliable or is it more of an afterthought/hack-around?
>
> I believe there is a "mysql" back-end to openldap. (might be postgresql
> though)
>
> IMO.. I wish postgresql would be more popular, as it really is a better
> database. :-P
>
> No, seriously, the problem is, LDAP is a protocol offering directory
> services,
> optimized for "read-mostly" data, the kind of thing you're likely to find
> in a phone book, DNS server or.. user account.
>
> I know it's a confusing mess, but it could be worse, you could be forced
> to use SOAP.
>
> Jamie
> --
> http://www.geniegate.com Custom web programming
> Perl * Java * UNIX User Management Solutions