Differences between version 36 and predecessor to the previous major change of CyrusNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 36 | Last edited on Thursday, March 23, 2006 4:28:02 am | by PaWell | Revert |
| Older page: | version 35 | Last edited on Friday, December 16, 2005 11:32:54 am | by DirkDuenkelmann | Revert |
@@ -74,8 +74,10 @@
''The best way to do this IMO is to make a sasl group on your system, make cyrus a member of this group, and give /var/run/saslauthd/ group +x permissions (only needs +x in order to be able to get into the dir, the actual socket on /var/run/saslauthd/mux is world +rwx anyway). This way, if you have other apps that use sasl, you just need to make them members of the sasl group as well and they can also read the socket. This is, AFAIK, the way the debian packages normally handle this -- DanielLawson''
''I slammed my head against this for some time before figuring out that even though openldap creates /etc/openldap/ldap.conf as it's ldap client default configuration file, other programs aren't looking for that file. They're looking for /etc/ldap.conf. The additions listed above for /etc/openldap/ldap.conf should actually be added to /etc/ldap.conf I figured this out by setting the loglevel on openldap to -1 and watching the conversation while doing a cyradm --user cyrus localhost -- ~EugeneWood''
+
+''In Debian create file /etc/pam_ldap.conf with content as in /etc/openldap/ldap.conf - it gives configuration to pam_ldap module "
''Here is what I was seeing in /var/log/messages Hopefully someone will catch this page from google with these terms -- ~EugeneWood''
<verbatim>
Sep 20 14:44:35 ''server'' perl: No worthy mechs found
