Which PingAM feature only uses the PingAM keystore?

Client-side sessions store session state in a signed and optionally encrypted JSON Web Token (JWT) held by the client. The cryptographic keys required for these operations are stored exclusively in the PingAM keystore. This makes the keystore the singular, essential server-side component for the security and integrity of client-side sessions. Other features listed use the keystore but also depend heavily on other components like the configuration data store for their overall function.

B: The Persistent Cookie node uses the keystore for signing but is part of a larger Authentication Tree framework that relies on the configuration store.

C: Authentication trees are a broad feature using many components; their reliance is not solely on the keystore.

D: OAuth2 providers use the keystore for token signing but rely extensively on the configuration store for client registration and policy information.

- Ping Identity, PingAM 7.5 Documentation, "Session management", section "Client-side sessions". The documentation states, "AM signs and, optionally, encrypts the JWT by using keys from its keystore."

- Ping Identity, PingAM 7.5 Documentation, "Core concepts", section "Keystores". This section describes the role of the keystore in storing keys for various cryptographic operations, including signing session tokens.