Set up a Fullstory connector

Capabilities
Gather Fullstory credentials
Generate a SCIM token
Configure the Fullstory connector

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Accounts

Gather Fullstory credentials

Configuring the connector requires a SCIM bearer token and your organization’s SCIM base URL, both 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 a SCIM token

For detailed instructions on enabling SCIM provisioning in Fullstory, see the official Fullstory SCIM configuration guide.

In Fullstory, navigate to Settings > Account Management > SSO.

Enable SCIM Provisioning if it is not already active.

Click Generate Token (or Regenerate Token if one already exists). Carefully copy and save the token — it will not be shown again.

Copy the SCIM Base URL shown on the same page. It typically looks like https://app.fullstory.com/scim/v2.

That’s it! Next, move on to the connector configuration instructions.

Configure the Fullstory 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

Cloud-hosted
Self-hosted

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

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

Search for Fullstory and click Add.

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

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.

Click Next.

Find the Settings area of the page and click Edit.

Paste your SCIM base URL into the SCIM Base URL field and your SCIM token into the SCIM Token field.

Click Save.

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

Follow these instructions to use the Fullstory 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. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Resources

GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Fullstory connector

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

Search for Baton and click Add.

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

Click Next.

In the Settings area of the page, click Edit.

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_SCIM_BASE_URL: <FullStory SCIM base URL>
  BATON_SCIM_TOKEN: <FullStory SCIM bearer token>

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
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-fullstory
        envFrom:
        - secretRef:
            name: baton-fullstory-secrets

Step 3: Deploy the connector

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

Check that the connector data uploaded correctly. In ConductorOne, click Apps. 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.

Set up Front connector

Set up a Galileo FT connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Fullstory connector

Capabilities

Gather Fullstory credentials

Generate a SCIM token

Configure the Fullstory connector

Resources

Step 1: Set up a new Fullstory connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather Fullstory credentials

​Generate a SCIM token

​Configure the Fullstory connector

​Resources

​Step 1: Set up a new Fullstory connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Fullstory credentials

Generate a SCIM token

Configure the Fullstory connector

Resources

Step 1: Set up a new Fullstory connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector