HowTo Imapd 3.4.1 and LDAP Authz ?

"Patrick Maweg" <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Hi,
I want to get imapd with ldap authz get running on RHEL 9 with the suplied rpm cyrus-imapd-3.4.1-6.el9.x86_64. 
I tried to use the same configuration I have used for RHEL 8 via saslauthd, but that does not work.

When I try to login with cyradm for testing I get the following log messages:

login: localhost [::1] patrick plaintext User logged in SESSIONID=<cyrus-1661160822-37408-1-4921340146338259975>
SASL SASL error opening password file. Have you performed the migration from db2 using cyrusbdb2current?
SASL Could not open /etc/sasl2/sasldb2
SASL unable to canonify user and get auxprops
badlogin: localhost [::1] SCRAM-SHA-1 (patrick) [SASL(-1): generic failure: unable to canonify user and get auxprops]
SASL SASL error opening password file. Have you performed the migration from db2 using cyrusbdb2current?
SASL Could not open /etc/sasl2/sasldb2
SASL unable to canonify user and get auxprops
badlogin: localhost [::1] SCRAM-SHA-256 (patrick) [SASL(-1): generic failure: unable to canonify user and get auxprops]
SASL SASL error opening password file. Have you performed the migration from db2 using cyrusbdb2current?
SASL Could not open /etc/sasl2/sasldb2
SASL unable to canonify user and get auxprops
badlogin: localhost [::1] DIGEST-MD5 (patrick) [SASL(-1): generic failure: unable to canonify user and get auxprops]
ldapdb
sql_select option missing
auxpropfunc error no mechanism available
auxpropfunc error invalid parameter supplied
ldapdb

First it seams to me the login is successful, but what does "SASL unable to canonify user and get auxprops" mean?

I would be grateful for any tips,
Best,
Patrick


------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T881a8b80728c403a-M19e9526179e54b2891755cc1
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.