[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: SASL /usr/lib/sasl2/App.conf configuration

To: OpenLDAP-Software@openldap.org
Subject: Re: SASL /usr/lib/sasl2/App.conf configuration
From: Francis Swasey <Frank.Swasey@uvm.edu>
Date: Wed, 17 Feb 2010 10:14:33 -0500
In-reply-to: <4B7BFEC9.3060503@uvm.edu>
References: <4B7BFEC9.3060503@uvm.edu>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/17/10 9:35 AM, Francis Swasey wrote:
> I am attempting to set up OpenLDAP 2.4 on an RHEL5 system.  I have applied patches that rename
> the OpenLDAP binaries to append 2.4 to the name, so it can co-exist with the standard RHEL5
> rpms without causing issues.
> 
> However, one unexpected side effect is that I don't know what it is now using as the name of
> the conf file in /usr/lib/sasl2.  In reading the SASL section of the Admin Guide, I was
> directed to read the cyrus sasl sysadmin.html which tells me to "Check your application's
> documentation for specifics".  Sadly, I can't find the specifics about how OpenLDAP is setting
> the SASL configuration file name in OpenLDAP's documentation.  Which of the fine documents do I
> need to read?

For future searchers -- I found it in servers/slapd/sasl.c (the call to sasl_server_init).  It
would be nice if the slapd.conf was specifically stated in the Admin Guide in the SASL
configuration section.

- --
Frank Swasey                    | http://www.uvm.edu/~fcs
Sr Systems Administrator        | Always remember: You are UNIQUE,
University of Vermont           |    just like everyone else.
  "I am not young enough to know everything." - Oscar Wilde (1854-1900)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLfAfZAAoJEK5S4SsZ5NvSTwgP/iQrCA4wIXIcEu8/SMf+g9Kb
Bmk+J/aDTXt3wvSDMNGwEzEVmdHa5dZ+XYQA0nwhhJCHncjV1xLBsYmvzHxIZldC
bnonxGe5oa+alog92LBWLkyyYZ8TRIcvwJ+6PpouHMmnM1PiuNZNEUTmittTANCK
5TF/2GxPt7xdVP8rTi5MnGDwASMxL1/pbmyHEV4Jtyxf6fudWRf8MzJtqTpyOG+b
1/hJhUAi5CwjGMWbECF31dHFkwqaXfMsTePGdwiKeWuShiC6QtcKv62eUN61VnyD
PGSQ6vdcOYGPv/zjhlQfJGGw/K4dcbwgWNqMG74gX8OOTXGwvE7bdyVg40pld3Iz
ifEEzyJcxcFrJnSbZZkjkrw2j6hkYSBSGAxy94z3LZjBlsIDY7lFMrfxzMVxLrUS
+0YthkYr2hPhZRcRUYHMG7lKeXihlnJtjRDi0XHHCQBor86YVONy0Ibaq4OvzAuL
sjBaXQQ+MtZv6SRAkRZ/d4GKS0sAkRQB4KQjM1+BBitHsLhnxFaIHsL+ptBlk46X
s8a3f+hD1dbIq0RKVtPs4uM2bP5TqqEnzP3rhde1otOBXbLR5Zgov9K8ESttWhbQ
aCJKzTxsobXHsHchPARPM66CuHp75ytvzJPsX7RcV4dsbTGgeXC+L07lJDHZQOVK
Qmc9HW25eJdlRLnL47TR
=Cgj/
-----END PGP SIGNATURE-----

References:
- SASL /usr/lib/sasl2/App.conf configuration
  - From: Francis Swasey <Frank.Swasey@uvm.edu>

Prev by Date: SASL /usr/lib/sasl2/App.conf configuration
Next by Date: Re: SASL /usr/lib/sasl2/App.conf configuration
Index(es):
- Chronological
- Thread