Contents x
    PingFederate
    • 12 Mar 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    PingFederate

    • Updated on 12 Mar 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    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:

    • Users
    • Application Extensions
    • User Extensions
    • SaaS Applications

    Parameters

    1. Host Name or IP Address (required) - The hostname or IP address of the PingFederate server that Axonius can communicate with via the Required Ports.

    2. Port (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.

    3. Authentication Method - Select if you want to authenticate with Basic Auth or OAUTH 2. The following fields are displayed based on the authentication method you select (see screenshots below).

      • Basic Authentication:
        • User Name and Password - The credentials for a an admin user account that has the permissions to fetch assets.
      • OAUTH 2:
        • Authorization URL (required) - The URL to authorize access via OAUTH2 (located in the <pf_install>/pingfederate/bin/oauth2.properties file).
        • Client ID and Client Secret - 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.
        • Scopes - Enter the scopes you want to grant for this connection.

    4. SSO provider - If your organization uses PingFederate for SSO, you can select this check box (selected by default). For more information, see Connecting your SSO Solution Provider Adapter.

    5. 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.

    6. HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

    7. 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.

    8. HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

    Adapter connection with Basic Auth authentication
    PingFederate_BasicAuth

    Adapter connection with OAuth2 authentication
    PingFederate_OAuth2

    To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.


    Advanced Settings

    Note:

    Advanced settings can either apply to all connections for this adapter, or to a specific connection. Refer to Advanced Configuration for Adapters.

    1. Fetch Users from dataStores - Select this option to fetch User Extensions from dataStores.
    2. Fetch OAuth clients - Select this option to fetch OAuth clients.
    Note:

    To learn more about Adapter Configuration tab advanced settings, see Adapter Advanced Settings.

    APIs

    Axonius uses the PingFederate API.

    Required Ports

    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


    Was this article helpful?
    What's Next