Set up a Snipe-IT connector

Capabilities
Gather Snipe-IT credentials
Generate an API token
Configure the Snipe-IT connector

Capabilities

Resource	Sync	Provision
Accounts
Groups
Permissions

Gather Snipe-IT credentials

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

Generate an API token

In the Snipe-IT web interface, click your user name and select Manage API keys.

Click Create New Token.

Carefully copy and save the new token.

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

Configure the Snipe-IT connector

To complete this task, you’ll need:

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

Choose how to set up the new Snipe-IT 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 Snipe-IT base URL into the Base URL field.

Paste the access token you generated in Step 1 into the Access 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 Snipe-IT connector is now pulling access data into ConductorOne.

Follow these instructions to use the Snipe-IT 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 Snipe-IT connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

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

Secrets configuration

# baton-snipe-it-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-snipe-it-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Snipe-IT credentials
  BATON_ACCESS_TOKEN: <Snipe-IT API key>
  BATON_BASE_URL: <Base URL for your Snipe-IT instance>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

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

Deployment configuration

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

That’s it! Your Snipe-IT connector is now pulling access data into ConductorOne.

Set up a Smartsheet connector

Set up a Snowflake connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Capabilities

Gather Snipe-IT credentials

Generate an API token

Configure the Snipe-IT connector

Step 1: Set up a new Snipe-IT 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 Snipe-IT credentials

​Generate an API token

​Configure the Snipe-IT connector

​Step 1: Set up a new Snipe-IT connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Snipe-IT credentials

Generate an API token

Configure the Snipe-IT connector

Step 1: Set up a new Snipe-IT connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector