# Keeper: SSO login errors with strict SP cert matching

> Keeper status incident “SSO login errors with strict SP cert matching” on 2025-07-06: impact none (vendor’s label), 0 min, 2 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/keeper/incidents/wgkry9jkksrw
Last updated: 2025-07-08T03:18:43Z

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2025-07-06 15:00 UTC · Resolved: 2025-07-06 15:00 UTC · Duration: 0 min
- Updates: 2
- [Vendor status page: https://stspg.io/qftkskxmy348](https://stspg.io/qftkskxmy348)
- [Company: Keeper](https://rewindex.com/company/keeper.md)

## Timeline of updates

- **resolved** 2025-07-06 15:00 UTC: Several customers have been experiencing SSO login errors this morning. The team determined the cause of the issue which is detailed in the postmortem report.
- **postmortem** 2025-07-08 03:18 UTC: On June 30, 2025, Keeper published an updated SAML Service Provider (SP) certificate as part of our standard annual process. This certificate is used for signing SP requests and does not impact SSL termination. During the update, the certificate subject name was unintentionally changed from sso.keepersecurity.com to sso.staging.keepersecurity.com. While most identity providers do not validate the certificate subject name, certain providers—such as JumpCloud and Shibboleth—may enforce strict matching and reject SAML requests when the subject name does not align. On Sunday July 6, 2025, routine backend infrastructure changes caused the cert to be propagated across production systems throughout the morning hours. The issue with the subject name was identified by our team after several troubleshooting calls with customers. The DevOps team then corrected the issue by publishing the certificate with the proper subject name around 12pm PST. After reviewing the case history, this affected a small number of customers. Next year, when the SP cert change is approaching, we will notify all customers with the exact date and time when the cert will be updated, so those customers using strict SP cert matching can be prepared. We apologize for the error and we have taken steps to ensure this does not occur again.

## Cite this

Status incident (vendor impact label: none) posted by Keeper, started 2025-07-06 15:00 UTC, resolved after 0 min, 2 update(s).

- Canonical URL: https://rewindex.com/company/keeper/incidents/wgkry9jkksrw
- Citation: Keeper, “SSO login errors with strict SP cert matching” (2025-07-06 15:00 UTC). Archived by Rewindex: https://rewindex.com/company/keeper/incidents/wgkry9jkksrw (CC BY 4.0).
- Markdown link: `[Keeper: SSO login errors with strict SP cert matching (2025-07-06)](https://rewindex.com/company/keeper/incidents/wgkry9jkksrw)`


---
Canonical: https://rewindex.com/company/keeper/incidents/wgkry9jkksrw · Markdown: https://rewindex.com/company/keeper/incidents/wgkry9jkksrw.md · JSON: https://rewindex.com/api/v1/companies/keeper/incidents/wgkry9jkksrw · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:22:20.878Z