Cyrus on CentOS with sasl / pam / ldap
- by Oscar
SASL/PAM/LDAP is driving me crazy... that's what I read a lot when googling for problems in this area, and what I experience myself :-S
I'm trying to get Cyrus imap working for virtual hosting on CentOS with this authorisation backend and really don't know what's happening.
In saslauthd I configured the LDAP search filter to use, but it looks like pam completely ignores it.
Here's what I do for testing (done more tests but all with similar results):
[root@testserv ~]# imtest -u [email protected].com -a [email protected].com
WARNING: no hostname supplied, assuming localhost
S: * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS] testserv. Cyrus IMAP4 v2.3.7-Invoca-RPM-2.3.7-7.el5_6.4 server ready
C: C01 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE IDLE LISTEXT LIST-SUBSCRIBED X-NETSCAPE URLAUTH
S: C01 OK Completed
Please enter your password:
C: L01 LOGIN [email protected].com {6}
S: + go ahead
C: <omitted>
S: L01 NO Login failed: authentication failure
Authentication failed. generic failure
Security strength factor: 0
C: Q01 LOGOUT
* BYE LOGOUT received
Q01 OK Completed
Connection closed.
The LDAP entry does exist (and so does the mailbox in Cyrus):
[root@testserv ~]# ldapsearch -WxD cn=Manager,o=mydomain,c=com [email protected].com
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base <> with scope subtree
# filter: [email protected].com
# requesting: ALL
#
# myuser, accounts, testserv.mydomain.com, mydomain, com
dn: uid=myuser,ou=accounts,dc=testserv.mydomain.com,o=mydomain,c=com
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
uidNumber: 16
uid: myuser
gidNumber: 5
givenName: My
sn: Name
mail: [email protected].com
cn: My Name
userPassword:: dYN5ebB0fXhNRn1pZllhRnJX7Uk=
shadowLastChange: 15176
homeDirectory: /dev/null
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
This is what I get in /var/log/messages
Aug 2 04:00:11 testserv cyrus/imap[12514]: auxpropfunc error invalid parameter supplied
Aug 2 04:00:19 testserv saslauthd[5926]: do_auth : auth failure: [[email protected]] [service=imap] [realm=testserv.mydomain.com] [mech=pam] [reason=PAM auth error]
... /var/adm/auth.log
Aug 2 04:00:11 testserv cyrus/imap[12514]: auxpropfunc error invalid parameter supplied
Aug 2 04:00:11 testserv cyrus/imap[12514]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: ldapdb
Aug 2 04:00:19 testserv saslauthd[5926]: DEBUG: auth_pam: pam_authenticate failed: User not known to the underlying authentication module
Aug 2 04:00:19 testserv saslauthd[5926]: do_auth : auth failure: [[email protected]] [service=imap] [realm=testserv.mydomain.com] [mech=pam] [reason=PAM auth error]
(AFAIK I can ignore the auxprop msg)
... and /var/log/slapd.log:
Aug 2 04:00:19 testserv slapd[5968]: conn=61 fd=27 ACCEPT from IP=127.0.0.1:51403 (IP=0.0.0.0:389)
Aug 2 04:00:19 testserv slapd[5968]: conn=61 op=0 BIND dn="" method=128
Aug 2 04:00:19 testserv slapd[5968]: conn=61 op=0 RESULT tag=97 err=0 text=
Aug 2 04:00:19 testserv slapd[5968]: conn=61 op=1 SRCH base="o=mydomain,c=com" scope=2 deref=0 filter="([email protected])"
Aug 2 04:00:19 testserv slapd[5968]: conn=61 op=1 SEARCH RESULT tag=101 err=0 nentries=0 text=
Aug 2 04:00:19 testserv slapd[5968]: conn=61 op=2 UNBIND
Aug 2 04:00:19 testserv slapd[5968]: conn=61 fd=27 closed
These are the settings in In /etc/imapd.conf:
sasl_mech_list: PLAIN LOGIN
sasl_pwcheck_method: saslauthd
## sasl_auxprop_plugin: sasldb
sasl_auto_transition: no
and my sasl config:
[root@testserv ~]# cat /etc/sysconfig/saslauthd
# Directory in which to place saslauthd's listening socket, pid file, and so
# on. This directory must already exist.
SOCKETDIR=/var/run/saslauthd
# Mechanism to use when checking passwords. Run "saslauthd -v" to get a list
# of which mechanism your installation was compiled with the ablity to use.
MECH=pam
# Additional flags to pass to saslauthd on the command line. See saslauthd(8)
# for the list of accepted flags.
FLAGS="-c -r -O /etc/saslauthd.conf"
[root@testserv ~]# cat /etc/saslauthd.conf
ldap_servers: ldap://127.0.0.1/
ldap_search_base: dc=%d,o=mydomain,c=com
ldap_auth_method: bind
#ldap_filter: (|(uid=%u)((&(mail=%u@%d)(accountStatus=active)))
ldap_filter: (&(mail=%u@%d)(accountStatus=active))
ldap_debug: 1
ldap_version: 3
The accountStatus=active is not in ldap yet, but that doesn't make a difference since I don't see it in the filter... that's not the reason for the failure.
The weird thing is, I do get an error when I rename or remove /etc/saslauthd.conf, but when the file exists it seems happily ignored...
The filter in slapd.log seems to be taken from /etc/ldap.conf. Apart from some timers, that only contains:
host 127.0.0.1
base o=mydomain,c=com
pam_login_attribute mail
Outcommenting the pam_login_attribute results in this filter in slapd.log:
filter="([email protected])"
Pam-imap looks like this:
[root@testserv ~]# cat /etc/pam.d/imap
auth required pam_ldap.so debug
account required pam_ldap.so debug
#auth sufficient pam_unix.so likeauth nullok
#auth sufficient pam_ldap.so use_first_pass
#auth required pam_deny.so
#account sufficient pam_unix.so
#account sufficient pam_ldap.so
The outcommented stuff is because I don't have the cyrus admin user in Ldap; that's a Linux user. That works fine when uncommented, but I still need to play around with that a little and first I wanna get imap working.
Finally nsswitch:
[root@testserv ~]# cat /etc/nsswitch.conf
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
# nisplus or nis+ Use NIS+ (NIS version 3)
# nis or yp Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files
# compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far
#
# To use db, put the "db" in front of "files" for entries you want to be
# looked up first in the databases
#
# Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis
passwd: compat ldap
group: compat ldap
shadow: compat ldap
hosts: files dns
bootparams: nisplus [NOTFOUND=return] files
ethers: files
netmasks: files
networks: files
protocols: files
rpc: files
services: files
netgroup: nisplus
publickey: nisplus
automount: files nisplus
aliases: files nisplus
Any info where to start looking will be greatly appreciated!
Thnx in advance
