Search…
⌃K

Cloud SSO Certificate Renewal 2022

Instructions on SSO certificate renewal in August 2022
Please read this document, as it affects Enterprise customers who use Keeper SSO Connect Cloud.
Note: Nothing needs to change on the Keeper side. Do NOT reconfigure your Keeper SSO settings. DO NOT delete anything. The only action you will take is updating Keeper's certificate on your identity provider.
  • On August 17 at 19:38 GMT (11:38 AM PST / 1:38 PM CST), Keeper's current Cloud SSO Certificate used for signing SAML requests is expiring. This is referred to as the Service Provider (SP) Certificate (Not the IdP Cert).
  • We have published a new Service Provider Certificate which is live and available for you to download. The certificate is embedded in the XML metadata file and also available as a direct download "Export SP Cert" from the Keeper Admin Console.

Who is NOT Affected?

  • Customers using basic configuration in Azure, Okta, Google are NOT Affected.
  • If you use Keeper Automator alongside SSO Cloud, you are NOT Affected and you do not need to update the certificate, as this is handled by the cert you added to Automator.
  • If you are using SSO On-Prem you are NOT Affected.

Who is Affected?

  • If you are using ADFS with Cloud SSO Connect (without Automator), you are affected.
  • If you are using Ping Identity (without Automator), you are affected. Read instructions below.
  • If you use Okta with SLO (Single Logout) activated, you are affected. Read instructions below.
  • If you use JumpCloud (without Automator), you are affected. Read instructions below.
  • If you are using service provider-initiated SLO (Single Logout) then you are affected.
  • If you have a configuration on your identity provider where they are encrypting the SAML assertion with our certificate, you will be affected -- if the identity provider refuses to encrypt with an expired cert.
  • Other identity providers may reject requests when the cert has expired.
  • It's best practice to update the certificate regardless.

What's the Resolution?

You can simply update the "Service Provider Certificate" in your identity provider (by uploading Keeper's Service Provider metadata or Service Provider Certificate). This can be done right now.
The metadata and SP Cert are available from the Keeper Admin Console as seen below:
Export Metadata and/or SP Cert

In Preparation

Important: Ensure that you have the ability to login to the Admin Console with an account and a Master Password that exists outside of the SSO node, in case your SSO is unavailable or affected by the expired certificate.
Updating the certificate only takes a few minutes.

ADFS Instructions

To update the service provider certificate on ADFS, please follow the below steps:
  1. 1.
    Login to the Keeper Admin Console
  2. 2.
    Go to Admin > SSO Node > Provisioning and then view the SSO Cloud configuration.
  3. 3.
    Click on "Export SP Cert" and save the certificate file.
  4. 4.
    In the AD FS Management Console select the Keeper Cloud SSO Relying Party Trust properties.
  5. 5.
    On the "Encryption" tab, replace the old certificate with this new cert.
  6. 6.
    On the "Signature" tab, Add/Replace the new SP certificate with this new cert.
AD FS Relying Party Trusts
Replace the Signing and Encryption Certificate

Azure Instructions

Azure does not appear affected by the certificate expiration, but updating the metadata is simple.
  • Go to Azure Portal > Enterprise Applications > Keeper Password Manager > Single Sign-On
  • Click "Upload metadata file" at the top.
  • Select the metadata xml file that was downloaded from Keeper.
  • Click Save

Okta Instructions

Only if you have enabled Single Logout enabled with Okta...
  • Login to the Keeper Admin Console
  • Go to Admin > SSO Node > Provisioning and then view the SSO Cloud configuration.
  • Click on "Export SP Cert" and save the certificate file.
  • Go to Okta Admin Portal > Applications > Keeper > Sign On tab
  • If you have "Enable Single Logout" enabled...
  • Click Edit and Upload the SP Cert from Keeper and click Save
  • If you don't have Single Logout enabled, there's nothing to do.

JumpCloud Instructions

  • Login to the Keeper Admin Console
  • Go to Admin > SSO Node > Provisioning and then view the SSO Cloud configuration.
  • Click on "Export SP Cert" and save the certificate file.
  • Go to the JumpCloud Admin Portal and go to SSO
  • Open the Keeper Application > SSO Tab
  • Click on "Replace SP Certificate" and select the new SP Certificate file. (NOT the IdP Cert!)
JumpCloud Instructions

Ping Identity Instructions

  • Login to the Keeper Admin Console
  • Go to Admin > SSO Node > Provisioning and then view the SSO Cloud configuration.
  • Click on "Export SP Cert" and save the certificate file.
  • Login to your Ping Identity portal.
  • Their notification center will notify you which certificates are expiring.
  • In the Ping portal, open the Keeper application
  • Update the "Verification Certificate" and the "Encryption Certificate".
  • (Alternatively, just upload the new Keeper metadata)

Instructions for other Identity Providers

  • Login to the Keeper Admin Console
  • Go to Admin > SSO Node > Provisioning and then view the SSO Cloud configuration.
  • Click on "Export SP Cert" and save the certificate file.
  • Click on "Export Metadata" and save the metadata file, which also contains the certificate.
  • Login to your Identity Provider portal and view the SSO configuration for Keeper.
  • Upload Keeper's SP certificate file (or metadata, if required) following their instructions to update the Service Provider certificate and Save.

Need help?

If you can't login to the Admin Console, please open a support case and we'll assist you. Make sure to provide all the relevant information about your identity provider and your environment.
If you require assistance, please open a support ticket at the link below:

Q&A

Q: Which certificate is updating?
A: Our SAML signing certificate for sso.keepersecurity.com has been renewed. The new certificate is now live and will be used for signing all requests until July 2023. This certificate is used for signing requests, sending Single Logout (SLO) requests and can be used to encrypt assertions from the Identity Provider (if configured that way).
Q: Are we affected?
A: In the document above, we identify which customers are affected. If you don't know, you should probably go ahead and update the certificate now, while the old cert is still valid. This is best practice.
Q: Is the key changing?
A: No, we are not re-keying the cert. The current certificate is simply being renewed. The public key does not change, only the expiration date of the cert.
Q: Why is this happening?
A: All certificates have to be renewed annually. Since 2020, public CAs have required that certificates must be renewed once per year (even if a multi-year certificate is purchased).
Q: Is SSO Connect On-Prem affected?
A: No, this only affects customers using SSO Connect Cloud.
Q: Why are we not affected if we use Automator?
A: When you set up Automator, the certificate used for signing comes from the Automator configuration, not from Keeper's certificate.
Q: How do we set up Automator?
A: The Keeper Automator service information is available here: https://docs.keeper.io/sso-connect-cloud/device-approvals/automator Keep in mind, Automator also requires a certificate that must be updated annually. It's just on a different time interval.