Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather PingFederate credentials

Each setup method requires you to pass in credentials generated in PingFederate. Gather these credentials before you move on.

To set up the PingFederate connector, you’ll need:

• Account username and password
• PingFederate doamin, in https://pingfederateserver.com format

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a PingFederate cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of PingFederate credentials generated by following the instructions above

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

2. Search for PingFederate and click Add.

   Don’t see the PingFederate connector? Reach out to support@conductorone.com to add PingFederate to your Connectors page.

1. Choose how to set up the new PingFederate connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

2. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

3. Click Next.

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

5. Enter your PingFederate instance URL (in the form https://pingfederateserver.com) in the INstance URL field.

6. Paste your PingFederate username and password into the Username and Password fields.

7. Click Save.

8. 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 PingFederate connector is now pulling access data into ConductorOne.

Set up a PingFederate self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of PingFederate credentials generated by following the instructions above

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. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the PingFederate connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new PingFederate connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

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. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your PingFederate connector deployment:

Secrets configuration

# baton-pingfederate-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-pingfederate-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # PingFederate-specific credentials
  BATON_INSTANCE_URL: <PingFederate domain, such as https://pingfederateserver.com>
  BATON_USERNAME: <PingFederate account username>
  BATON_PASSWORD: <PingFederate account password>

  # Optional: Include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

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

Deployment configuration

# baton-pingfederate.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-pingfederate
  labels:
    app: baton-pingfederate
spec:
  selector:
    matchLabels:
      app: baton-pingfederate
  template:
    metadata:
      labels:
        app: baton-pingfederate
        baton: true
        baton-app: pingfederate
    spec:
      containers:
      - name: baton-pingfederate
        image: ghcr.io/conductorone/baton-pingfederate:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-pingfederate-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-pingfederate-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-pingfederate.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-pingfederate}
   

3. 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 PingFederate connector to. PingFederate data should be found on the Entitlements and Accounts tabs.

That’s it! Your PingFederate connector is now pulling access data into ConductorOne.