My Favorites

Close

Please to see your favorites.


SLMS certificate configuration file being changed.

This document (7007997) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Lifecycle Management Server 1.2

Situation

If you use certificates in SLMS and have them configured in /etc/apache2/vhosts.d/slms/smls_vhost-ssl.conf
For example:
   SSLCertificateFile /etc/slms.d/certs/certificate-example.net.cert.pem
   SSLCertificateKeyFile /etc/slms.d/certs/certificate-example.net.key
   SSLCACertificateFile /etc/slms.d/certs/intermediate-example.crt

You will need to make a copy of your changes in slms_vhost-ssl.conf and after the SLMS code update move them to /etc/apache2/vhosts.d/slms_ssl_options.include

Cause

Customer was using a VeriSign certificate bundle and had their configuration in the /etc/apache2/vhosts.d/slms/smls_vhost-ssl.conf file.
When we updated the SLMS rpms their custom configuration for using the VeriSign certificates would be removed thus the certificates would not be working. 
ERROR: Peer certificate cannot be authenticated with known CA certificates:

Therefore the new configuration file was created to hold these changes /etc/apache2/vhosts.d/slms_ssl_options.include this file will not exist until you have the newer SLMS code is installed.

Additional Information

This code change is avaliable in slms-1.2.8-0.3.1 released June 7, 2012.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7007997
  • Creation Date:24-MAY-12
  • Modified Date:11-JUN-12
    • SUSESUSE Lifecycle Management Server

Did this document solve your problem? Provide Feedback