We setup up the Samanage SSO via SAML that connects to Azure Active Directory per the documentation that exists here:
Within the Samanage/Setup/Single Sign-On screen, our x.509 (provided by Azure AD) certificate changes and we are required to update it to enable single sign on to work. Microsoft is changing those keys (which impacts the x.509 certificate required by Samanage) often and without notice, as documented here and those consuming applications, namely Samanage in our case, will need to support those key changes automatically.
Microsoft has provided documentation on how to build and update applications that integrate and support Azure Active Directory so the certificate can be updated automatically and won’t impact the application.
I'd like to know if there is something we can do with current setup to mitigate this issue or if there are plans with Samanage to change the way that the certs are handled so that it could deal with the automatic rollover when new keys are generated by Microsoft.