The way mod_admserv works now is that it only does NSS initialization if mod_nss is being used. But mod_nss is only for the server side of TLS/SSL. mod_admserv needs to be able to speak LDAPS to the directory server even if it is not a TLS/SSL server itself.
Created attachment 157430 [details] diffs
Your changes look good.
Reviewed by: nhosoi (Thanks!) Fix Description: The way the code currently works is that mod_admserv let's mod_nss do all of the NSS initialization. But mod_nss is only used when the admin server is also a TLS/SSL server. mod_admserv still needs to do NSS initialization when it is a TLS/SSL client (e.g. of the config DS using LDAPS). This fix allows mod_admserv to do the client side TLS/SSL init. Platforms tested: RHEL4 Flag Day: no Doc impact: no Index: mod_admserv.c =================================================================== RCS file: /cvs/dirsec/mod_admserv/mod_admserv.c,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- mod_admserv.c 11 May 2007 19:46:36 -0000 1.29 +++ mod_admserv.c 19 Jun 2007 23:31:12 -0000 1.30