- 03 Aug 2023
- 1 Minute to read
- Updated on 03 Aug 2023
- 1 Minute to read
PingFederate from Ping Identity is an enterprise authentication federation server that enables user authentication and single sign-on.
Types of Assets Fetched
This adapter fetches the following types of assets:
- SaaS Data
Host Name or IP Address of your PingFederate Admin Node (required) - The hostname or IP address of the PingFederate server that Axonius can communicate with via the Required Ports.
Port Number of API Key (required) - The API endpoint is available at the administrative port as defined in the pf.admin.https.port property. See
Accessing the API interactive documentation for more information.
Authorization URL for OAUTH2 (required) - The URL to authorize access via OAUTH2 (located in the <pf_install>/pingfederate/bin/oauth2.properties file). If you don't configure the adapter to access PingFederate via OAUTH2, then you'll need to enter the username and password parameters.
Client ID and Client Authentication Password - The Client ID and Client Secret for an account that has read access to the API. These parameters are located in the <pf_install>/pingfederate/bin/oauth2.properties file.
Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name (optional) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.
HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
User Name and Password - The credentials for a an admin user account that has the permissions to fetch assets. This is only needed if you don't configure the adapter to access PingFederate via OAUTH2.
To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.
Axonius uses the PingFederate API.
Axonius must be able to communicate with the value supplied in Host Name or IP Address via the following ports:
- 9999 or as defined in run.properties file on the Ping Federate node.
Adapter Integration Setup
Follow instructions in the PingFederate documentation to generate the following parameters for the adapter connection form.
- Authorization URL for OAUTH2
- Client ID
- Client Authentication Password
Supported From Version
Supported from Axonius version 5.0.