Set up an ADP Workforce Now connector

ConductorOne provides identity governance and just-in-time provisioning for ADP Workforce Now. Integrate your ADP Workforce Now instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

Capabilities

The ADP Workforce Now connector syncs the following resources:

Resource	Sync	Provision
Organization Position
Worker

Gather ADP Workforce Now credentials

To configure the ADP Workforce Now connector, you need administrator permissions in ADP Workforce Now.

1. Navigate to the ADP Marketplace Developer portal and register your application.

2. Obtain your OAuth2 client credentials:

   1. Copy the Client ID and Client Secret
   2. Download the SSL client certificate (PEM-encoded .pem or .crt file)
   3. Download the SSL private key (PEM-encoded .pem or .key file)
   4. Save these credentials securely — ADP requires mTLS authentication

Configure the ADP Workforce Now connector

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

1. In ConductorOne, navigate to Integrations > Connectors and click Add connector.

2. Search for ADP Workforce Now and click Add.

3. Choose how to set up the new ADP Workforce Now connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter the required configuration:

   • Client ID (adp-workforce-now-client-id): Your ADP OAuth2 client ID
   • Client Secret (adp-workforce-now-client-secret): Your ADP OAuth2 client secret
   • SSL Certificate (adp-workforce-now-ssl-cert): PEM-encoded SSL client certificate for mTLS
   • SSL Key (adp-workforce-now-ssl-key): PEM-encoded SSL client private key for mTLS
   • Base URL (adp-workforce-now-base-url): The ADP API base URL (default: https://api.adp.com)
8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your ADP Workforce Now connector is now pulling access data into ConductorOne.

Self-hosted

Follow these instructions to use the ADP Workforce Now connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals.

Step 1: Set up a new ADP Workforce Now connector

1. In ConductorOne, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new ADP Workforce Now connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your ADP Workforce Now connector deployment:

Secrets configuration

# baton-adp-workforce-now-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-adp-workforce-now-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

  # ADP Workforce Now credentials
  BATON_ADP_WORKFORCE_NOW_CLIENT_ID: <ADP OAuth2 client ID>
  BATON_ADP_WORKFORCE_NOW_CLIENT_SECRET: <ADP OAuth2 client secret>
  BATON_ADP_WORKFORCE_NOW_SSL_CERT: <path to PEM SSL client certificate>
  BATON_ADP_WORKFORCE_NOW_SSL_KEY: <path to PEM SSL private key>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-adp-workforce-now.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-adp-workforce-now
  labels:
    app: baton-adp-workforce-now
spec:
  selector:
    matchLabels:
      app: baton-adp-workforce-now
  template:
    metadata:
      labels:
        app: baton-adp-workforce-now
        baton: "true"
        baton-app: adp-workforce-now
    spec:
      containers:
      - name: baton-adp-workforce-now
        image: public.ecr.aws/conductorone/baton-adp-workforce-now:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-adp-workforce-now
        envFrom:
        - secretRef:
            name: baton-adp-workforce-now-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the ADP Workforce Now connector to. ADP Workforce Now data should be found on the Entitlements and Accounts tabs.

That’s it! Your ADP Workforce Now connector is now pulling access data into ConductorOne.

---

All versions of this connector are available at dist.conductorone.com.