Skip to main content

ADP Workforce Now

Visualize ADP Workforce Now workers and departments in the JupiterOne graph, map the employee reporting hierarchy, correlate workers to their user accounts, and monitor changes through queries and alerts.

Installation

Prerequisites

  • An ADP Workforce Now account with access to the ADP HR APIs.
  • ADP-issued API credentials for a registered API application: an OAuth Client ID and Client Secret, plus a client SSL certificate and its private key (PEM).
  • Access to JupiterOne with permission to configure integrations.

Obtain ADP API credentials

The integration authenticates to the ADP Workforce Now APIs using OAuth 2.0 (client credentials) together with mutual TLS — every request presents a client SSL certificate in addition to a bearer token. ADP issues the required credentials to a registered API application:

  • a Client ID and Client Secret (the OAuth client credentials), and
  • a client SSL certificate and its private key (PEM), registered with ADP for the mutual-TLS handshake.

These credentials are provisioned by ADP through the ADP developer program. Work with your ADP representative or ADP's developer documentation to register an API application, obtain the Client ID and Client Secret, and generate the client certificate and key. The application must be granted access to the worker and department data this integration reads — see the Authorization tab for the specific permissions and endpoints.

The integration issues read-only requests.

Configure the integration in JupiterOne

To install the ADP Workforce Now integration in JupiterOne, navigate to the Integrations tab and select ADP Workforce Now. Click New Instance to begin configuring your integration.

Creating an ADP Workforce Now instance requires the following:

  • The Account Name used to identify the ADP Workforce Now account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.
  • Description to assist in identifying the integration instance, if desired.
  • Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.

Authentication fields

FieldRequiredDescription
Client IDYesThe ADP OAuth client ID for your registered API application.
Client SecretYesThe ADP OAuth client secret for your registered API application.
Client Certificate (PEM)YesThe PEM-encoded client SSL certificate registered with ADP for mutual TLS. Paste the entire file contents, including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.
Client Key (PEM)YesThe PEM-encoded private key paired with the client certificate, for mutual TLS. Paste the entire file contents, including the -----BEGIN ... PRIVATE KEY----- header and footer lines.

Advanced

These fields are optional and only needed to override the default ADP endpoints.

FieldDefaultDescription
API Base URLhttps://api.adp.comOverride the ADP API base URL. Leave blank to use the default.
OAuth Token URLhttps://accounts.adp.com/auth/oauth/v2/tokenOverride the ADP OAuth token endpoint. Leave blank to use the default.

Click Create once all values are provided to finalize the integration.

Next steps

Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.