Bug 235143 - Default nsslapd-saslpath setting is incorrect on non-Linux platforms
Default nsslapd-saslpath setting is incorrect on non-Linux platforms
Product: 389
Classification: Community
Component: Security - SASL (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nathan Kinder
Viktor Ashirov
Depends On:
Blocks: 152373 240316 FDS1.1.0
  Show dependency treegraph
Reported: 2007-04-03 18:29 EDT by Nathan Kinder
Modified: 2015-12-07 12:17 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-07 12:17:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
CVS Diffs (1.40 KB, patch)
2007-04-03 18:29 EDT, Nathan Kinder
no flags Details | Diff

  None (edit)
Description Nathan Kinder 2007-04-03 18:29:34 EDT
When you create a new instance on a non-Linux platform, the nsslapd-saslpath
setting in dse.ldif is incorrect.  It is currently set to <sroot>/sasl2, but the
sasl plugins are actually installed in <prefix>/<libdir>/sasl2.  This causes the
server to not load any of it's SASL plugins, so it doesn't advertise any
mechanisms other than EXTERNAL.

The attached diffs set the proper path for the nsslapd-saslpath setting.
Comment 1 Nathan Kinder 2007-04-03 18:29:35 EDT
Created attachment 151628 [details]
CVS Diffs
Comment 2 Nathan Kinder 2007-04-03 19:09:33 EDT
Checked into ldapserver (HEAD).  Thanks to Rich and Noriko for their reviews!

Checking in create_instance.c
/cvs/dirsec/ldapserver/ldap/admin/src/create_instance.c,v  <--  create_instance.c
new revision: 1.53; previous revision: 1.52

Note You need to log in before you can comment on or make changes to this bug.