Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Auth0 credentials

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

A user with the ability to create a new application in Auth0 must perform this task.

Create an Auth0 application

1. In Auth0, navigate to Dashboard > Applications > Applications and click Create Application.

2. Give the new application a name, such as “ConductorOne”.

3. Select the Machine to Machine Applications option and click Create.

4. Select the management API for your domain.

5. Give the application’s access token the following permissions:

   • read:users
   • read:grants
   • read:organizations
   • read:organization_members
   • read:roles
   • read:role_members

6. Click Authorize.

7. On the Application Settings page, click Settings.

8. Carefully copy and save the Client ID and Client Secret for the application.

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

Set up an Auth0 cloud-hosted connector

To complete this task, you’ll need:

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

1. In ConductorOne, click Connectors > Add connector.

2. Search for Auth0 and click Add.

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

1. Choose how to set up the new Auth0 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. In the Base URL field, enter the base URL for your Auth0 instance in https://companyname.auth0.com format.

6. In the Client ID and Client Secret fields, enter the credentials.

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

Set up an Auth0 self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Auth0 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 Auth0 connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new Auth0 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 Auth0 connector deployment:

Secrets configuration

# baton-auth0-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-auth0-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Auth0 credentials
  BATON_AUTH0_BASE_URL: <Base URL of the Auth0 instance>
  BATON_AUTH0_CLIENT_ID: <Auth0 app client ID>
  BATON_AUTH0_CLIENT_SECRET: <Auth0 app client secret>

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

Deployment configuration

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

Step 3: Deploy the connector

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

   kubectl create namespace baton-auth0
   

2. Apply the secret configuration:

   kubectl -n baton-auth0 apply -f baton-auth0-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-auth0 apply -f baton-auth0.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-auth0}
   

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

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