Last Modified: Dec 20, 2018
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
Opened: Jul 03, 2017
TMM cores if the SAML message signature verification certificate cannot be found in the configuration.
The issue can lead to momentary service interruption. Traffic disrupted while tmm restarts.
-- SAML is configured with an invalid certificate in the message signature validation setting. -- The control-plane is unable to detect such misconfiguration. Note: This is an unlikely occurrence if the usual control-plane is used to configure the SSO/SAML object. In this particular case, the certificate-key was passed in as the certificate which triggered a certificate-not-found error.
Make sure the certificate configured for use with the SAML message signature verification is correctly configured and the configuration loads successfully.