Contribute  :  Support  :  Downloads  :  Forum  :  Links  :  Polls  :  Calendar  :  Directory  :  Advanced Search  
Geeklog The Ultimate Weblog System
Welcome to Geeklog
Friday, May 16 2008 @ 01:48 AM EDT
   

LDAP Support?

ServerI am playing with LDAP for some IMAP stuff I am doing at work. Eventually I will need to have Geeklog and my IMAP server work together so that account creation, password updates and authentication work seemlessly between the two.

For that it seems that using LDAP makes the most sense. Aside from that it would take Geeklog a long way from being a toy for Geeks to a realistic intranet solution for businesses and organizations that already use LDAP.

On the other hand adding LDAP support could break the KISS principle (Keep-it-Simple-Stupid). What are the pros and cons to adding the LDAP authentication to Geeklog? Would you use it or would it be just a waste of time?

Story Options

LDAP Support? | 5 comments | Create New Account
The following comments are owned by whomever posted them. This site is not responsible for what they say.
My .02
Authored by: Anonymous on Wednesday, January 09 2002 @ 03:33 AM EST
My two cents are that this would get some use, but how much use it would see is dependent upon the LDAP management and setup tools available in other products. At my job, I\'ll be putting in a MacOS X Server system this summer. I\'ve been told that it can export its user authentications through LDAP. We\'re already using IMAP on a FreeBSD server, too. We use IMAP authentication for several web apps.

My suggestion is to take the following steps:
1) Abstract the current authentication system out of the code base and put it in something like lib/auth/standalone.php.
2) Write the LDAP stuff and put it in lib/auth/ldap.php
3) If you want, write some IMAP authentication stuff and put it in lib/auth/imap.php
4) Make a variable in config.php that reads the correct authentication library. Each file has the same variable names and function names and the same output format, so it would be easy to interchange them.

I have seen this done successfully. I started down this path on a project that I ran a year and a half ago and this is how TWIG works. I know you hate TWIG, but this is one of its good points and it actually does work.

Anyway, if GeekLog had the above setup today, I\'d grab the IMAP authenticator in a heartbeat. Once the MacOS X Server controlled logins on our MacOS workstations, I\'d consider switching to LDAP. Since its not available today, I\'d probably wait until the MOSXS system is in place and then look into its LDAP tools. I\'d make up my mind mostly based on the feelings of my users and the ease of the LDAP system administration. I have a feeling that you\'ll see that a lot, too. LDAP is a great tool that most geeks have at least heard of. Many/most of us haven\'t started using it only due to the complexity of setup within the classic text-only environment of Linux and BSD.

Hope my babbling helps. :)
Good ideas
Authored by: Tony on Wednesday, January 09 2002 @ 06:35 AM EST
First, let me say I don\'t hate TWIG. I used TWIG for a year and some generally annoyances pushed me to try other things and I settled on SquirrelMail.

Your ideas on implementing authentication in Geeklog is right on and farily easy to do. Would you be willing to contribute the IMAP authentication module? I can seperate the current standalone stuff and possibly the LDAP stuff.

Who am I talking to anyway?
I _will_ love it!!
Authored by: tbehle on Wednesday, January 09 2002 @ 03:40 PM EST
We have LDAP authentication for everything we were able to
get it for: IMAP, webmail, netatalk (via pam_ldap), squid-auth.
Everything uses the same database - it\'s great!
LDAP Authentication
Authored by: jimphelps on Friday, October 11 2002 @ 12:44 PM EDT
This is an old thread but here goes...

I would love to see an LDAP authentication/account management module for Geeklog.

- Jim
LDAP Support?
Authored by: Mathelart on Wednesday, December 04 2002 @ 01:13 AM EST
It should be a really great improvement to Geeklog !
But if you don\'t have time, and if it\'s not too complicated (the concerned source code is limited to one php file, not ten), maybe I could try ...