Raju Mathur spewed into the ether:
>1. It'd be simpler to stick to LDAP since that is likely to remain as
>a standard for user-type databases. Most protocol implementations
>(e.g. SMTP, POP3, IMAP4, HTTP, PAM, etc) handle LDAP authentication
>out of the box. The same is not true of PgSQL or MySQL (or any other
>SQL implementation).
All the s/w I noted can use a SQL backend (According to Suresh, Postfix can, which is
the only thing I wasn't sure about).
>LDAP interface. Once you've migrated all servers to use the PgSQL
>auth, you can do away with LDAP altogether. Or maybe not: I still
>have to see a PGSQL:// equivalent URI akin to LDAP:// for net-oriented
>searches.
This data is internal to the organization. Users may access and/or modify their own
data, but will have no access to other data anyway.
All access for users is web based, for admins, command line.
>3. Do have a look at VishwaKarma. It does most of the things you
>want, using LDAP. Version 2 is in the works, and I'd be happy if
>someone can spend some time to help me finish it and locate some basic
>packages which I can steal and put into VishwaKarma.
I did, if you remember my asking you for help earlier with OpenLDAP-2.0.7. I did post
my slapd.conf, and got no responses.
Will try to migrate VK to 2.0.7, but again all data is being
duplicated.
If CVS is available on Kandalaya, I'll get on with updating my version
and modifying as necessary.
Devdas Bhagat
------------------------------------------------------------
For Valentine's Day shop by Brand, Product, Price, Store and Location!
http://shop.storerunner.com/shop.asp?pdef=home&trsid=3080
----------------------------------------------
An alpha version of a web based tool to manage
your subscription with this mailing list is at
http://lists.linux-india.org/cgi-bin/mj_wwwusr
