Step 1: Check if your IdP validates signed SAML requests
Check whether your IdP validates the signature on SAML authentication requests. This setting is often called "signed requests" or "verification certificate". Refer to the IdP-specific sections below and your IdP vendor's documentation for how to check this setting.
- If this setting is not enabled: no action is required, and this change will not affect sign-in to Clarity SaaS.
- If this setting is enabled: Complete the remaining steps in this article. For IdP-specific instructions, see the sections below and your IdP vendor's documentation.
Step 2: Obtain the new certificate
The new certificate can be obtained from the Broadcom SAML metadata URL or the certificate file can be downloaded from this Knowledge Base article.
Step 3: Update your IdP
- If your IdP supports multiple verification certificates, add the new certificate before the change window and keep the existing one active. Do not remove the old certificate yet.
- If your IdP supports only one certificate, do not change it early. Replace it at the change time, November 21, 2026 at 01:00 UTC.
IdP-specific guidance
IdP type | Action | Timing |
Supports multiple certificates | Add the new certificate as secondary; keep the old one | Before the change window |
Supports a single certificate only | Replace the certificate at the cutover time | At November 21, 2026 at 01:00 UTC |
Reads metadata automatically | Confirm your IdP accepts both certificates in the metadata | Before and after the window |
Restricted / managed by a third party | Coordinate the swap with the IdP vendor | Agree timing in advance |
Step 4: Validate after the change window
- Sign in to Clarity SaaS via SSO.
- Confirm the IdP is validating with the new certificate.
Guidance for Customers configuring different IDP Providers
Microsoft Entra ID (formerly Azure AD): Use these steps as a guide and confirm against your IdP vendor documentation.
- Entra admin center > Enterprise applications > select the Clarity SaaS application > Single sign-on.
- Under SAML Certificates, open Verification certificates > Edit and check whether "Require verification certificates" is selected. If it is not, Entra ID does not check request signatures and no action is needed.
- If it is selected, upload the new certificate. Entra ID accepts more than one verification certificate, so keep the existing one in place.
- If sign-in fails after the change window with error, the request is unsigned or signed with a certificate that is not uploaded. Confirm the new certificate is present.
OKTA: Use these steps as a guide and confirm against your IdP vendor documentation.
- Okta Admin Console > Applications > select the Clarity SaaS SAML application > General tab > SAML Settings > Edit, then Next to reach the SAML configuration page, then Show Advanced Settings.
- Check whether "Signed Requests" is selected. This checkbox only appears once a Signature Certificate has been uploaded. If no certificate is uploaded, no action is needed.
- If it is selected, at the change time, November 21, 2026 at 01:00 UTC, upload the new certificate in the Signature Certificate field, replacing the existing one. Okta allows only one active Signature Certificate for incoming signed SAML requests. If you add it before Broadcom's cutover, SSO authentication will fail immediately for Clarity SaaS users.
- Save, then validate SSO login to Clarity SaaS.
Ping: Use these steps as a guide and confirm against your IdP vendor documentation.
PingFederate
- Go to : Applications > Integration > SP Connections > select the Clarity SaaS connection > Credentials > Signature Verification Settings > Manage Signature Verification Settings.
- Confirm the trust model is Unanchored. The Clarity SaaS signing certificates are self-signed and do not chain to a CA, so Unanchored is the model that applies.
- Before the change window, add the new certificate as an additional verification certificate and keep the existing certificate in the list. PingFederate accepts a signature that verifies against any certificate in the list, so sign-in keeps working before and after the cutover.
PingOne
- Open the Clarity SaaS SAML application > Configuration and check whether Enforce Signed Authentication Request is turned on. If it is off, no action is required.
- If it is on, upload the new verification certificate at the change time, November 21, 2026 at 01:00 UTC, replacing the existing certificate. Do not upload it earlier. Until the cutover, Broadcom still signs requests with the current certificate, and an early swap would make sign-in fail.
- Test sign-in after the change time.
Other Identity Providers
Systems that automatically retrieve SAML metadata
If your IdP retrieves Broadcom SAML metadata automatically: the metadata already lists both certificates. Confirm that your SAML implementation or library accepts both ds:X509Certificate entries and validates a request signed with either one. If it can trust only one, update it at the change time.
Systems using manually configured certificates
If your IdP uses a manually configured certificate: download the new certificate (.crt, attached at the end of this article) before the change time.
- If your IdP supports multiple trusted certificates: add the new certificate before the change window and keep the existing one. After Broadcom begins signing with the new certificate, confirm sign-in works, then remove the old certificate.
- If your IdP supports only one certificate: at the change time, November 21, 2026 at 01:00 UTC, replace the existing certificate with the new one.