Bug 235143

Summary: Default nsslapd-saslpath setting is incorrect on non-Linux platforms
Product: [Retired] 389 Reporter: Nathan Kinder <nkinder>
Component: Security - SASLAssignee: Nathan Kinder <nkinder>
Status: CLOSED CURRENTRELEASE QA Contact: Viktor Ashirov <vashirov>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0.4   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-07 17:17:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 152373, 240316, 427409    
Attachments:
Description Flags
CVS Diffs none

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