Feb 14, 2010
pam_imap is a PAM module that authenticates against a remote IMAP or IMAPS server.pam_imap program supports multiple servers, SSL, password caching, user blacklists (for admin users), and many configuration abilities.Examples of recommended use: 1) A lab of UNIX/Linux machines that would require an easily accessible password database from an IMAP server 2) Authenticating users against a centralized password server that you have no control over, and it conveniently has an IMAP server. (The arms-tied-behind-your-back scenario) 3) Authenticating with applications that do not run as root. (Apache is a good example -- read user-testimonials below) 4) An IMAP cluster authentication relay -- pam-imap can be used for a cheap IMAP cluster solution. Have one or two master IMAP servers that have a username/password database (be it LDAP, shadow, etc) and an IMAP server. Have several cluster node servers to handle the bandwidth of client requests , and use pam-imap on each node to authenticate against the master server(s).
(The node machines will use pam-imap in their 'imap' service file)Tie everything together with round-robin DNS and NFS mail folders, and you have yourself an IMAP cluster! Here are some key features of "pam_imap":
· User BlockList: Allows pam-imap to ignore authenticating users such as 'root', 'apache', and others.
· Password caching: Possibly usefull in situations where network connections are slow, or server loads are high. Has a few security risks however. Checkout the README file for more info.
· Support for firstname.lastname@example.org style logins. With Micro$oft style IMAP servers, the "@domain.com" can be appended to the UNIX username for easy compatability.
· Customizable "Password: " string... You could change it to anything! Maybe, "IMAP Password: " The possibilities are endless.
What's New in This Release:
· This release fixes a few non-critical typos.
· The RPM package has been updated.