Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Fullstory credentials

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

A user with the Admin or Architect role in Fullstory must perform this task.

Generate an API key

1. In Fullstory, navigate to your account’s API Keys page and click Create key.

2. Give the API key a name, such as “ConductorOne”.

3. Select either Admin or Architect permissions for the key.

4. Click Save API Key, then carefully copy and save the new key.

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

Set up a Fullstory self-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-fullstory-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-fullstory-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Fullstory credentials
  BATON_API_KEY: <Fullstory API key>

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

Deployment configuration

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

Step 3: Deploy the connector

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

   kubectl create namespace baton-fullstory
   

2. Apply the secret configuration:

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

3. Apply the deployment:

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

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

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