Specific tables are required in order for PingFederate to store grants, the associated attributes, and their values (if any), on your database server. Table-setup scripts are provided for supported database servers.
- Run the table-setup scripts for your database server provided in the <pf_install>/pingfederate/server/default/conf/access-grant/sql-scripts directory.
- If you have not already done so, create a JDBC data store for your database server on .
- Copy the System ID of the applicable Java Database Connection (JDBC) data store from the Data Stores window.
For a clustered PingFederate environment, edit this file on the administrative console node first, and then replicate to other engine nodes using as explained in later steps.
<c:item name="PingFederateDSJNDIName"/>element value with the system ID of your data store connection and save the file.
If the system ID is
JDBC-123456789ABCDEF123456789ABCDEF123456A0A6, update the org.sourceid.oauth20.token.AccessGrantManagerJdbcImpl.xml file as follows.
<?xml version="1.0" encoding="UTF-8"?> <c:config xmlns:c="http://www.sourceid.org/2004/05/config"> <c:item name="PingFederateDSJNDIName">JDBC-123456789ABCDEF123456789ABCDEF123456A0A6</c:item> </c:config>
- Replace the
Go to the
# Service for storage of access grantssection.
access.grant.managerservice endpoint to the following:
... access.grant.manager=org.sourceid.oauth20.token.AccessGrantManagerJdbcImpl ...
In clustered PingFederate environments, you must manually edit the service-points.conf file on each node because cluster replication can't replicate this change to other nodes.
- Go to the
Start or restart PingFederate.
For a clustered PingFederate environment, replicate this new configuration to other engine nodes on . Start or restart the PingFederate service on each engine node to activate the change.
PingFederate provides two cleanup tasks for persistent grants. One task manages expired grants, while another task caps the number of grants based on a combination of user, client, grant type, and authentication context. For more information, see OAuth persistent grants cleanup.