ConductorOne docs

Set up a Fastly connector

ConductorOne provides identity governance and just-in-time provisioning for Fastly. Integrate your Fastly instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts	✅
Roles	✅	✅
Services	✅	✅

Gather Fastly credentials

Configuring the connector requires you to pass in credentials generated in Fastly. Gather these credentials before you move on.

A user with the Superuser role in Fastly must perform this task.

Create a Fastly automation API token

In Fastly, click on your account name in the top navigation bar and select Account.
Click API tokens.
Click Create Token.
On the Create a Token page, give the new API token a name (such as “ConductorOne”).
In the Type area of the page, select Automation token and fill out the form as follows:
- Role: Select Engineer
- TLS management: leave the box unchecked
- Scope: Select Read-only access
- Access: Select the relevant services or all services, as appropriate
- Expiration: If you set an expiration date, remember that the connection with ConductorOne will fail if the token expires.
Click Create Token.
The new token is generated. Carefully copy and save the token.

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

Configure the Fastly connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Fastly credentials generated by following the instructions above

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

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Fastly and click Add.
Choose how to set up the new Fastly 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 the automation API token into the API 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 Fastly connector is now pulling access data into ConductorOne.

Follow these instructions to use the Fastly 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.

Step 1: Set up a new Fastly connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Fastly 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.
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 Fastly connector deployment:

Secrets configuration

# baton-fastly-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-fastly-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Fastly credentials
  BATON_ACCESS_TOKEN: <Fastly API token>

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

Deployment configuration

# baton-fastly.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-fastly
  labels:
    app: baton-fastly
spec:
  selector:
    matchLabels:
      app: baton-fastly
  template:
    metadata:
      labels:
        app: baton-fastly
        baton: true
        baton-app: fastly
    spec:
      containers:
      - name: baton-fastly
        image: ghcr.io/conductorone/baton-fastly:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-fastly-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 Applications. On the Managed apps tab, locate and click the name of the application you added the Fastly connector to. Fastly data should be found on the Entitlements and Accounts tabs.

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