Updating Certificates for SSO with SAMLv2

Updating Certificates for SSO with SAMLv2

When using SSO with SAMLv2 as the authentication method, you may encounter temporary access issues after updating your certificate. To ensure a smooth transition, keep the following in mind:

Key Points to Remember

  • Certificate propagation time
    After updating the certificate both in your SSO provider and in your RunMyProcess account (e.g., Google), it may take some time for the changes to propagate across systems.

  • User login issues
    If users experience access problems during this period, ask them to log out of their SSO account and log in again. This often resolves the issue.

👉 For more details on configuring SSO with SAMLv2, see the RunMyProcess documentation.

    • Related Articles

    • Migrating to OAuth for Office 365 Mail in RunMyProcess

      Microsoft is retiring Basic Authentication for Office 365. For details, see the official announcement: https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750 Overview To use ...

    • Resolving Gmail SMTP Error

      If you're encountering the following error when attempting to send a notification via Gmail as an SMTP provider: "Service Unavailable (503) - 535-5.7.8 Username and Password not accepted," it’s likely due to recent changes in Google’s security ...