Capabilities
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.
Configure the Fullstory connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in C1
- Access to the set of Fullstory credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.In C1, navigate to Apps > Connectors and click Add connector.
Search for Fullstory and click Add.
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
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.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
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 C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 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 C1, navigate to Apps > Connectors and click Add connector.
Search for Baton and click Add.
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
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
See the connector’s README or run --help to see all available configuration flags and environment variables.Deployment configuration
Step 3: Deploy the connector
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In C1, 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.
