Set up a Linode connector

Capabilities
Gather Linode credentials
Generate an authentication token
Configure the Linode connector

Capabilities

Resource	Sync	Provision
Accounts
Permissions

Gather Linode credentials

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

Generate an authentication token

In Cloud Manager, navigate to your profile menu and select API Tokens.

Click Create a Personal Access Token.

Give the new token a name, such as “ConductorOne”, and set an expiration.

Select the Read Only permission for Accounts.

Click Create Token. Carefully copy and save the new token.

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

Configure the Linode connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Linode 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 Admin > Connectors and click Add connector.

Search for Linode and click Add.

Choose how to set up the new Linode 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.

Enter your token into the Linode authentication token field.

Enter the Linode API URL you use in the Linode API URL field. Default is https://api.linode.com/v4/.

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

Follow these instructions to use the Linode 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: Configure the Linode connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

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

Secrets configuration

# baton-linode-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-linode-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Linode credentials
  BATON_TOKEN: <Linode API token>
  BATON_API_URL: <Linode API URL - Default is "https://api.linode.com/v4/">

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

Deployment configuration

# baton-linode.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-linode
  labels:
    app: baton-linode
spec:
  selector:
    matchLabels:
      app: baton-linode
  template:
    metadata:
      labels:
        app: baton-linode
        baton: true
        baton-app: linode
    spec:
      containers:
      - name: baton-linode
        image: ghcr.io/conductorone/baton-linode:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-linode
        envFrom:
        - secretRef:
            name: baton-linode-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 Linode connector to. Linode data should be found on the Entitlements and Accounts tabs.

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

Set up a Linear connector

Set up a Litmos connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up a Linode connector

Capabilities

Gather Linode credentials

Generate an authentication token

Configure the Linode connector

Step 1: Configure the Linode connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather Linode credentials

​Generate an authentication token

​Configure the Linode connector

​Step 1: Configure the Linode connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Linode credentials

Generate an authentication token

Configure the Linode connector

Step 1: Configure the Linode connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector