Bug 235143 - Default nsslapd-saslpath setting is incorrect on non-Linux platforms
Summary: Default nsslapd-saslpath setting is incorrect on non-Linux platforms
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Security - SASL
Version: 1.0.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nathan Kinder
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 152373 240316 FDS1.1.0
TreeView+ depends on / blocked
 
Reported: 2007-04-03 22:29 UTC by Nathan Kinder
Modified: 2015-12-07 17:17 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-07 17:17:58 UTC
Embargoed:

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

Description Nathan Kinder 2007-04-03 22:29:34 UTC 
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 22:29:35 UTC 
Created attachment 151628 [details]
CVS Diffs
Comment 2 Nathan Kinder 2007-04-03 23:09:33 UTC 
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
done
Note You need to log in before you can comment on or make changes to this bug.