IBM Support

Confirming MAS Certificate Validity

How To


Summary

Maximo Application Suite uses RedHat cert-manager to automatically manage SSL/TLS certificates. Alternatively, manual certificate management can be enabled to allow public transport layer security (TLS) certificates to be uploaded manually.

Objective

This document provides guidance on information to collect, and initial troubleshooting steps when encountering a certificate-related issue in MAS.

Steps

Check existing certificates:
  1. From the OpenShift console, go to 'Workloads'> 'Secrets' and select the MAS Core project.
  2. Search for "public" and select the "xxxx-cert-public" secret.OCP Console: Workloads>Secrets>public cert
  3. Using OpenSSL or other tools, view contents of the content of the tls.crt.viewing certificate contents using openssl
  4. Confirm that the certificate is still valid and contains the correct Subject Alternative Names (SANs)
  5. Repeat if needed for other MAS application projects.
If custom domain has been implemented:
  1. From the OpenShift console, go to 'Administration'> 'CustomResourceDefinitions' >search and select: "Suite"
  2. Go to 'Instances' tab and select your Suite CR.
  3. Select 'YAML' and go to the spec.domain section and confirm that the domain value matches the one in the certificate. 
If manual certificate management is enabled:
  1. Confirm that the certificates used for MAS Core and other applications share the same certificate authority.
  2. Ensure that the certificate/s contains all the required Subject Alternative Names (SANs) for each application. 

Document Location

Worldwide

[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000hAeeAAE","label":"Maximo Application Suite-\u003ECore"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Type":"MASTER"}]

Document Information

Modified date:
19 June 2025

UID

ibm17157663