Keeper Security 5 Jahre in Folge als Leader im Bereich Passwortverwaltung ausgezeichnet
Mehr erfahren
+ 
Teams sign in to Keeper with their Ping credentials while all passwords and secrets remain encrypted end-to-end. Built on SAML 2.0, with support for both PingOne and legacy Ping Identity.
Keeper connects to Ping over SAML 2.0. Users authenticate with their Ping identity, and Keeper enables an encrypted, zero-knowledge vault behind that login, without connectors or custom code. Setup runs through the Keeper Admin Console and the Ping Application Catalog, with the exact path depending on whether you run PingOne or Ping Identity.
Set up an SSO Connect Cloud method in Keeper, then add the Keeper application in Ping. The two exchange SAML details so they trust each other. PingOne does this with a metadata and certificate exchange; older Ping Identity setups use a couple of values entered manually.
Keeper reads First, Last and Email from Ping, and access follows the Ping groups you assign. The people and permissions you already manage in Ping carry straight into Keeper.
Once live, users reach their vault through their Ping identity. After the first sign-in, a single email address routes them straight to Ping, with no separate password to manage.
Ping gets users through the door, and Keeper gives them an encrypted vault for the passwords, secrets and connections that SSO alone doesn't cover. Anything not tied to the identity provider still lives in a secure location and is governed by the same login.
Keeper SSO Connect Cloud runs as a cloud service, so there's no application server to provision, secure or patch. Teams that prefer a self-hosted deployment can use SSO Connect On-Prem instead.
With just-in-time provisioning, Keeper creates a user's account the first time they authenticate through Ping, so there's no separate setup to run or keep in sync. New hires reach their vault as soon as they land in the right Ping group.
Keeper grants vault access based on the Ping groups assigned to the application. Leave it open to everyone, or scope it to specific groups, and keep access aligned with the structure admins already manage.
After the first sign-in, Keeper routes users straight to Ping from a single email address. There's no domain to remember and no master password to type.
Ping verifies the user; Keeper encrypts what they store on the device, with keys that never leave it. Admin SSO changes how people log in, not who can see their data, so vault contents remain invisible to Keeper and Ping alike, and zero knowledge stays intact.
With Keeper, give every employee a secure vault behind the login they already use and make strong password habits the default.
Both PingOne and legacy Ping Identity. In the Keeper Admin Console, set the IDP Type to PingOne for PingOne or Generic for legacy Ping Identity.
Yes, SSO Connect Cloud is the recommended path for most organizations, but SSO Connect On-Prem is available for teams that need a self-hosted deployment on their own Windows or Linux server.
Existing users move from the root node into the SSO-enabled sub-node. On their first login after the move, they may be prompted to confirm with their master password once, then authenticate through Ping from then on.
Three: First, Last and Email. The names are case-sensitive and must start with a capital letter, since lowercase values cause parsing errors during setup.
Confirm that just-in-time provisioning is enabled in the Keeper SSO configuration and that the email domain is reserved with Keeper. Domain reservation is what routes an email to the correct SSO connection.
Sie müssen Cookies aktivieren, um den Live-Chat zu nutzen.