Page created: 22 Jul 2020
|
Page updated: 1 Feb 2021
Configure an access token validator to use PingFederate OAuth tokens with PingDirectory.
You need the following information:
- The runtime engine service port of the PingFederate server, usually 9031
- The client ID of an OAuth 2.0 client configured on the PingFederate server
- The client secret of the OAuth 2.0 client
- The IP address of the PingFederate server
After you configure a PingFederate server to issue OAuth 2 tokens, you must make these tokens compatible with SCIM 2.0 operations on PingDirectory Server or PingDirectoryProxy Server.
This section explains how to set up an access token validator to handle this task.