Overview
When your organization renews its Single Sign-On (SSO) certificate, you may wonder if you need to send the updated certificate or Metadata XML file to our support team.
In most cases, no action is required on your part, and you do not need to send us your renewed certificate—as long as your SSO configuration parameters remain unchanged.
When Update Is NOT Required
You do not need to submit a new certificate or contact support if:
You are simply renewing an expiring SSL/SAML certificate within your Identity Provider (IdP) (e.g., Azure AD / Entra ID, Okta, Google Workspace).
The SSO Authentication URI / Endpoint URL remains exactly the same.
Your SSO Issuer / Entity ID has not changed.
Because our system authenticates users via your established SSO Authentication URI, standard certificate renewals on your Identity Provider's end will not interrupt user login or access.
When You DO Need to Contact Support
You only need to send us updated SSO details if there are structural changes to your Identity Provider setup, such as:
A change to your SSO Authentication URI / Endpoint URL.
A change to your Entity ID / Issuer URL.
Switching to an entirely new Identity Provider (e.g., migrating from ADFS to Okta).
Frequently Asked Questions
Will our users experience login downtime when our SSO certificate renews?
No. As long as the Authentication URI remains identical, your users can continue logging in seamlessly without any disruption or manual updates required on our side.
What should we do if our SSO Authentication URI changes?
If your URI or endpoint changes, please submit a support ticket with your new Authentication URI and updated Metadata XML file prior to the migration date so our technical team can update your site configuration.
Need Assistance?
If you are unsure whether your SSO changes affect your Authentication URI, please contact our support team, and we will be happy to verify your configuration.