Skip to main content
Question

Connector for monitoring the expiry of an Azure Enterprise Application SAML certificate

  • May 28, 2026
  • 1 reply
  • 7 views
S
Forum|alt.badge.img+11

Background:

  • This is not an App Registration.
  • The requirement relates to an Enterprise Application configured with Single Sign-On (SSO) using SAML.
  • This SAML SSO uses a signing certificate with an expiry date.
  • We would like to track this expiry date in Centreon so that we can plan for renewal and avoid any service disruption.

Questions:

  • Is there a plugin pack, connector, or Centreon monitoring method that allows us to retrieve the expiry date of this certificate?
  • If this is not supported natively, is there a method recommended by Centreon for monitoring it, for example via Microsoft Graph, an API, or a custom script?
  • If specific development is required, could you confirm the most suitable approach for integrating this properly into Centreon?

We would also be interested in any documentation, configuration examples, or best practices on this subject.

Thank you in advance for your feedback.

My forum signature

    1 reply

    ltirand
    Centreonian
    Forum|alt.badge.img+12
    • ltirand
    • Centreonian
    • June 5, 2026

    Hello :)

    Is there a plugin pack, connector, or Centreon monitoring method that allows us to retrieve the expiry date of this certificate?

    Currently, there is no native connector that covers this specific use case. The existing Azure and Office 365 connectors do not include any check for SAML signing certificate expiry on Enterprise Applications.

     

    If this is not supported natively, is there a method recommended by Centreon for monitoring it?

    An alternative approach, without writing a full plugin, would be to use HTTP Collections : a Centreon feature that allows querying REST APIs through a JSON configuration file. However, this would involve a multi-step collection (OAuth2 authentication + Graph API call + array filtering + date arithmetic), which is a fairly advanced use case. A tutorial on how to build HTTP Collections is available here. 

     

    If specific development is required, could you confirm the most suitable approach for integrating this properly into Centreon?

    There are two paths forward depending on your resources and timeline:

    Option 1 : Develop the plugin yourself and submit a Pull Request

    If you have development resources available, you are welcome to contribute a plugin to the Centreon open-source repository. Contributions can be submitted as a Pull Request here

    Option 2 : Submit an idea on The Watch and let the community vote

    If you would prefer Centreon to handle the development, the right channel is to submit a feature request as an idea on The Watch idea. Ideas are visible to the whole community and can be upvoted, which helps us prioritize roadmap items.

     

    Hope this helps

    Best regards.

    Alone we go faster, together we go further.
    Terms & ConditionsAccessibility statement