[turba] ldap user auth

[Terry Davis]

well you kinda touched on exactly what I am doing.
horde uses my imap server for auth.  my imap server uses my ldap server for auth.  that way, horde doesnt have to go through the work of configuring and talking directly to an ldap server.  
Why would you want to mix and match your authentication stuff?  In theory, all of your users are part of the same authentication system whether it be ldap,sql,ftp,imap, or whatever.  If not, each module (i think) has its own authentication hooks so you can specify each one individually.

excuse me but I really have little clue about what I am talking about so <slap> me if I am out of line.

Thank you,

-- 
Terry Davis
Systems Administrator
BirdDog Solutions, Inc.
(402) 829-6059


Quoting Edwin Culp <eculp@EnContacto.Net>:

> This is a complex issue and one that I haven't seen a solution that I
> can live with.  
> <possible brain fart>
> In an ideal world, I would like to login to horde once and have it send my
> login information to the other horde modules if they are configured for 
> horde authentication.  If they aren't configured for horde you would log 
> in to each individually.  I would want to have multiple database options
> such as ldap, mysql, pgsql and unix password.
> 
> This is making me wonder, why we couldn't mix and match?  Use the horde 
> login information taken from ldap to login to an imap/pop3/ftp server that 
> is authenticating from the unix password file?  (This being a configuration
> option, of course.)  I'm sure I'm missing something.
> </possible brain fart>
> 
> ed
> 
> Quoting Julian Jares <julian@jares.com.ar>:
> 
> | Quoting Terry Davis <tdavis@birddog.com>:
> | 
> | > [...] 
> | > Yes.  If I can at least get that information in a variable somehow
> | > (securely), then it _should_ be easy to implement that into the
> | > /turba/config/sources.php file.  This I will have to learn a bit of php
> | for
> | > but that is not a big deal.   Chuck hinted that this might be a bad idea.
> 
> | I
> | > am guessing there might be security concerns if we start throwing the
> | auth
> | > information around.  
> | 
> | I think Chuck is not worried about security (in this matter), but for 
> | the "integrity" of the framework. You can actually use turba without imp
> | right 
> | now, but if you add that modification, you will be imp dependant for
> turba.
> | 
> | Maybe the right way to go is to add functions (or function hooks) for 
> | authentication (and user information) in horde, but I just don't know if
> | that's 
> | too much work.
> | I do agree private addressbooks are a must have.
> | 
> | -- 
> | Julian
> | 
> | -- 
> | Turba mailing list: http://horde.org/turba/
> | Frequently Asked Questions: http://horde.org/faq/
> | To unsubscribe, mail: turba-unsubscribe@lists.horde.org
> | 
> | 
> 
> 
> 
> 
> ---
> 
> -- 
> Turba mailing list: http://horde.org/turba/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: turba-unsubscribe@lists.horde.org
> 


-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/