Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Redis credentials

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

To set up the integration with ConductorOne, you’ll need:

• Your Redis Enterprise Service cluster host and port

• The username and password for a Redis user (or service account) with admin permissions

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

Set up a Redis cloud-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Redis Enterprise and click Add.

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

1. Choose how to set up the new Redis 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 Cluster host field, enter your Redis Enterprise Service cluster host.

6. In the API port field, enter the enterprise API port (defaults to 9443).

7. In the Username and Password fields, enter the login credentials for a Redis user with admin permissions.

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

Set up a Redis self-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-redis-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-redis-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Redis credentials
  BATON_CLUSTER_HOST: <The cluster host for your Redis Enterprise Service>
  BATON_API_PORT: <The Redis Enterprise admin port (defaults to 9443)>
  BATON_USERNAME: <Redis account username>
  BATON_PASSWORD: <Redis account password>

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

Deployment configuration

# baton-redis.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-redis
  labels:
    app: baton-redis
spec:
  selector:
    matchLabels:
      app: baton-redis
  template:
    metadata:
      labels:
        app: baton-redis
        baton: true
        baton-app: redis
    spec:
      containers:
      - name: baton-redis
        image: ghcr.io/conductorone/baton-redis:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-redis-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-redis-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-redis.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-redis}
   

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

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