How to Manage SAML Certificates in Make.com

This guide explains how to manage SAML certificates in make.com so you can keep SSO access secure, handle expiring certificates, and avoid authentication issues for your team.

All instructions below are based on the official documentation for SAML certificate management and walk you through every step in a simple, practical way.

Understanding SAML Certificates in Make.com

Before changing any configuration, it helps to understand what SAML certificates do in make.com and why they matter.

When you enable SAML single sign-on for your organization, your SAML identity provider (IdP) uses a certificate to sign authentication assertions. Make.com then verifies these signatures using the certificate details stored in your SSO settings.

If the certificate expires or changes and is not updated in make.com, users may no longer be able to sign in using SSO.

Key roles of SAML certificates in Make.com

Authenticate users: Certificates ensure that SSO responses really come from your IdP.
Protect against tampering: Signed assertions prevent modification of identity data in transit.
Control SSO trust: Only IdPs with the correct certificate are trusted by make.com.

For more background, you can check the original help article on SAML certificate management.

Where to Manage SAML Certificates in Make.com

SAML certificate settings live in the organization-level SSO configuration inside make.com. Only organization admins with access to SSO settings should make changes here.

Accessing SSO settings in Make.com

Sign in to your make.com account using an admin user that can manage the organization.
Open the organization menu (usually from your profile or organization switcher).
Navigate to the security or SSO / SAML configuration page.
Locate the SAML configuration where your identity provider is defined.

On this page, you will see certificate-related fields and options that control how make.com validates SAML assertions from your IdP.

How Make.com Handles SAML Certificate Expiration

Certificates have a defined validity period. To help you avoid unexpected SSO outages, make.com includes controls and notifications for SAML certificate expiration.

Expiration visibility in Make.com

In your SAML configuration, you will typically see:

The current certificate details imported from your IdP.
The certificate expiration date, if provided by the IdP metadata.
Warnings if the certificate is close to expiring.

These indicators help you plan a rotation before the certificate reaches its end date.

Certificate expiration alerts

Make.com may notify administrators when a certificate is approaching expiration. These alerts can be delivered through:

On-screen warnings in the SSO configuration area.
Notifications or emails, depending on your account settings.

When you receive such alerts, you should coordinate with your IdP administrator to schedule a certificate update.

Rotating SAML Certificates in Make.com

Certificate rotation means replacing an old certificate with a new one before it expires. The exact steps differ slightly depending on your identity provider, but the process in make.com follows a consistent pattern.

Step 1: Prepare a new certificate in your IdP

Log in to your SAML identity provider’s administration console.
Generate or upload a new signing certificate according to your organization’s security policies.
Configure your SAML application (service provider configuration) to use the new certificate, often by editing the SAML app or profile that represents make.com.
Download the updated IdP metadata file or copy the new certificate and related SAML settings.

Do not delete the old certificate yet unless your IdP specifically requires immediate replacement; you may need a short overlap period.

Step 2: Update SAML settings in Make.com

In make.com, go back to the SSO / SAML configuration area for your organization.
Locate the section for certificate or IdP metadata.
Either upload the new IdP metadata file or paste the new certificate into the provided field, depending on how your SSO integration is set up.
Save your changes to apply the new certificate configuration.

Once saved, make.com will use the new certificate to validate SAML assertions.

Step 3: Test SSO after updating the certificate

Open a new browser session or private window.
Attempt to log in to make.com using SSO as a test user.
Confirm that the authentication flow completes successfully without errors.

If login fails, double-check that the certificate and metadata you configured in both your IdP and make.com match and that the certificate is valid for signing SAML assertions.

Replacing an Expired or Invalid SAML Certificate

If the certificate has already expired or become invalid, users may experience sign-in failures. In that case, you need to restore SSO as quickly as possible.

Emergency recovery steps in Make.com

Ask an admin who still has direct credentials (non-SSO) to sign in to make.com.
Open the organization’s SAML configuration page.
Retrieve new certificate or metadata from your IdP admin.
Update the certificate fields with the new data.
Save and test SSO logins again.

If no one can access the account because all users rely on SSO, you may need to use account recovery options provided by make.com support to regain access and then correct the SAML configuration.

Best Practices for SAML Certificate Management in Make.com

To reduce risk and keep SSO stable, follow these best practices when managing certificates in make.com.

Monitor certificate lifecycles

Track certificate expiration dates in your internal documentation.
Schedule reminders well in advance of expiration (for example, 60 and 30 days before).
Regularly review SSO settings in make.com to confirm no warnings are present.

Coordinate with your IdP administrator

Plan certificate rotations during low-usage periods.
Ensure that changes in the IdP are mirrored promptly in make.com.
Use metadata files when possible to reduce manual copy/paste errors.

Test and validate after each change

Use test accounts or staging environments if available.
Have at least one admin keep non-SSO credentials for emergency access to make.com.
Communicate upcoming SSO maintenance windows to your users.

Troubleshooting SAML Certificate Issues in Make.com

Problems with SAML certificates often appear as login errors or SSO failures. You can troubleshoot these by reviewing your configuration both in the IdP and in make.com.

Common symptoms

Users receive a generic SSO error instead of being signed in.
Make.com logs show invalid signature or certificate problems.
SSO suddenly stops working around the certificate expiration date.

Quick troubleshooting checklist

Verify the certificate in the IdP matches the certificate stored in make.com.
Confirm that the certificate is marked for signing SAML assertions.
Check that the certificate is still within its validity period.
Review any recent changes made either in the IdP or in make.com SSO settings.
Re-upload metadata if you suspect the configuration is out of sync.

If you continue to experience issues, consult the official documentation on SAML certificate management or contact support through your make.com account.

Additional Resources Beyond Make.com Documentation

For strategy, process design, and broader automation consulting that complements what you configure in make.com, you can also review resources at Consultevo. They provide advisory services that can help you integrate SSO and automation workflows into a wider technical roadmap.

For the exact and latest product-level details, always refer to the original article on SAML certificate management, as it reflects current behavior and options inside the platform.

By following the steps and best practices in this guide, you can keep SAML certificates correctly configured in make.com, prevent SSO interruptions, and maintain a secure, reliable authentication experience for all organization members.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help