Using custom solutions for persistent session storage - PingFederate

Using custom solutions for persistent session storage - PingFederate - 12.0

PingFederate Server

bundle

pingfederate-120

ft:publication_title

PingFederate Server

Product_Version_ce

PingFederate 12.0 (Latest)

category

Administrator

Administratorguide

Audience

Capability

ContentType

DeploymentMethod

Guide

Product

Productdocumentation

SingleSignonSSO

Software

SystemAdministrator

pf-120

pingfederate

ContentType_ce

Product documentation

Guide

Guide > Administrator Guide

The PingFederate SDK supports custom storage for persistent authentication sessions.

Implement the SessionStorageManager interface.

Note: For more information, see the Javadoc for the SessionStorageManager interface. The Javadocs for PingFederate are in the <pf_install>/pingfederate/sdk directory.

Edit the <pf_install>/pingfederate/server/default/conf/service-points.conf file:

Go to the # Service for storing Authentication Sessions section.

# Service for storing Authentication Sessions.
# Supported classes:
#   org.sourceid.saml20.service.session.data.impl.SessionStorageManagerJdbcImpl : Use this service-point for a Jdbc implementation.
#   org.sourceid.saml20.service.session.data.impl.SessionStorageManagerLdapImpl : Use this service-point for an LDAP implementation.
#   org.sourceid.saml20.service.session.data.impl.SessionStorageManagerDynamoDBImpl : Use this service-point for a DynamoDB implementation.
session.storage.manager=org.sourceid.saml20.service.session.data.impl.SessionStorageManagerJdbcImpl

Change the value of the session.storage.manager service to the name of your class.

Note:

For a clustered PingFederate environment, you must edit the service-points.conf file on each node manually because cluster replication can't replicate this change to other nodes.

Deploy the required program files of your custom implementation to all PingFederate servers.
Start or restart PingFederate.

Note:
For a clustered PingFederate environment, replicate this new configuration to other engine nodes on System > Server > Cluster Management. Start or restart the PingFederate service on each engine node to activate the change.