Ping Identity Built Enterprise Federation. The Federation Depends on Shared Secrets.
by Nick Clark | Published March 28, 2026
Ping Identity provides enterprise federation, single sign-on, and API security through industry-standard protocols including SAML, OAuth 2.0, and OpenID Connect. The federation model allows identities to be asserted across organizational boundaries. But every federation relationship depends on shared secrets: signing certificates, client secrets, and token encryption keys that both parties must maintain. A compromised federation certificate breaks the trust relationship across every relying party. The gap is between federated identity management and an identity primitive that does not depend on shared key material.
Ping Identity's federation depth, adaptive authentication, and API security capabilities serve real enterprise needs. The gap described here is about the federation protocol's dependency on shared secrets, not about Ping's implementation quality.
Federation requires shared key material
SAML federation requires signing certificates exchanged between the identity provider and each service provider. OAuth 2.0 requires client secrets or certificate-based client authentication. OpenID Connect adds ID tokens signed with keys that relying parties must be able to verify. Every federation relationship is built on shared or published key material.
When these keys are compromised, rotated, or expired, the federation relationship breaks until new key material is exchanged. The operational burden of certificate management across hundreds of federation relationships is substantial. The key material is the foundation that federation trust stands on.
Token-based identity is credential-based identity
Federation produces tokens: SAML assertions, OAuth access tokens, and OIDC ID tokens. These tokens are time-limited credentials. They must be stored during their lifetime, transmitted securely, and validated at each relying party. A stolen token provides the bearer with the identity it represents until the token expires.
Shorter token lifetimes reduce the window of vulnerability but increase the frequency of authentication events. The fundamental model remains: identity is proven by presenting a credential artifact.
What keyless identity addresses
Keyless identity would enable federation without shared secrets. Each party's identity would derive from its accumulated behavioral continuity, validated through trust slope functions. A federation relationship would not depend on exchanged certificates or shared keys. It would depend on the continuous behavioral validation of each participating entity.
A compromised certificate would not break the federation because the federation does not depend on certificates. Each entity's identity is its own continuity, independently verifiable without shared material.
