How to receive an alert when the server certificate is about to expire



1. Introduction

Don't you hate it when you get in to work one morning to find your OES/eDirectory services that worked the night before don't work anymore. When you find that the problem is due to server certificate expiration, don't you wish that there is some way to inform you before the certificate expires so that you can fix it beforehand. This document explains how this can be done.

2. Understanding the solution

The solution requires you to download a bash script, which means that you can only run this script on an OES server or SLES with eDirectory. The script retrieves all server certificates expiration via LDAP and checks against the current month and year. If the certificates expire within the same month or has already expired, the administrators will be notified via email. If the certificate is going to expire on the same day that the script is run, a special warning will be sent to inform the administrators that they should repair the certificates immediately.

This script should be configured to run on the 1st day of the month at 12:00am. The worst case scenario is that the server certificate has expired on the 1st day of the month before the start of the work day (e.g. at 1am). In this case, the administrators should have already received an email at 12am and repairing the certificate would be the first task of the day.

3. Implementing the solution

3.1. Download the '' script to your OES/eDirectory server (e.g. /usr/local/bin) and make changes to the following variables accordingly.

Variables Description This is your company's domain name. Make sure it is a valid one because an email will be sent to your administrator using this domain
These are the emails of your administrators who will receive the email alerts. Use a space to separate the emails. This is the domain name or IP address of eDirectory server or OES contains a replica of all servers' OU. Pointing to your Master replica server is a safe bet.Note: This server should allow LDAP search via port 389. To allow LDAP via port 389, open iManager -> LDAP -> LDAP options -> LDAP Group.SERVERNAME -> Uncheck 'Require TLS for Simple Binds with Password'

If port 389 is not allowed, change the script to use 636 accordingly (look for the ldapsearch command within the script).
Organization='o=novell' This is the Organization name configured on the eDirectory Tree. If your servers are located across multiple organization, then use the tree name instead e.g. Organization='T=novell-tree'

3.2. Configure crontab to run this script on the 1st of every month at 12am.
Modify the /etc/crontab accordingly ->

0 0 1 * * root /usr/local/bin/ 2>/dev/null

3.3. Configure postfix to enable sending of email.

  • Ensure postfix service is started by typing the following command. The status should show that the service is running ->
/etc/init.d/postfix status
  • Ensure postfix service is started at run time by typing the following command.
chkconfig postfix on
  • Edit the /etc/postfix/ file and ensure that the following line is included into this file
transport_maps = hash:/etc/postfix/transport
  • Find out the IP address (or DNS address) of your SMTP server (e.g. Edit the /etc/postfix/transport file and ensure that the following line is included into this file. Change the IP address below accordingly
* smtp:
  • Type the following command. Verify that this command updates the /etc/postfix/transport.db file
/sbin/postmap /etc/postfix/transport
  • Finally, try sending an email to yourself by typing the following command on the server. Change to your company's domain and youremail to your actual email. Leave $HOST as it is.
echo “this is a test email” | mail -r $ -s “This is a test subject”

4. Testing the solution

You can test this solution by creating 2 certificates that will expire today and expire at the end of the month. Run the script manually and see whether you will receive emails alerts.

To create custom server certificates, do the following:

  • Open iManager -> Novell Certificate Server -> Create Server Certificate
  • Step 1 of 6: Choose the server that you want to create the certificate on. Choose 'Custom' as the creation method.
  • Step 2 of 6: Choose Organizational certificate authority
  • Step 3 of 6: Leave everything as default
  • Step 4 of 6: Under Validity period, choose 'Specify dates'. Select the Expiration date as either today or end of the month.
  • Step 5 of 6: Choose Your organization's certificate
  • Step 6 of 6: Click Finish.

Note: This solution was tested successfully on an OESSP3 server.

Special thanks to Aska Hsu from China Engineering Consulting Inc. for bringing up this request and testing this solution.


Chris Seamons
Micro Focus Community Management
If you find this post useful, give it a 'Like' or use 'Verify Answer'.


How To-Best Practice
Comment List
Related Discussions