Set up a NINJIO connector

C1 provides identity governance for NINJIO. Integrate your NINJIO instance with C1 for unified visibility and governance over user access.

Capabilities

The NINJIO connector syncs the following resources:

Resource	Sync	Provision
Employees
Campaigns
Simulations

Gather NINJIO credentials

To configure the NINJIO connector, you need administrator permissions in NINJIO.

1. Log in to the NINJIO admin portal at admin.goninjio.com.

2. Navigate to your account or API settings and generate an API key.

3. Copy the API key and save it securely. You will need it to configure the connector.

Configure the NINJIO connector

Cloud-hosted

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

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

2. Search for NINJIO and click Add.

3. Choose how to set up the new NINJIO connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter the required configuration:

   • API Key: Your NINJIO API key
8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your NINJIO connector is now pulling access data into C1.

Self-hosted

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

Step 1: Set up a new NINJIO connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new NINJIO connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your NINJIO connector deployment:

Secrets configuration

# baton-ninjio-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-ninjio-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # NINJIO credentials
  BATON_NINJIO_API_KEY: <your NINJIO API key>

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

Deployment configuration

# baton-ninjio.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-ninjio
  labels:
    app: baton-ninjio
spec:
  selector:
    matchLabels:
      app: baton-ninjio
  template:
    metadata:
      labels:
        app: baton-ninjio
        baton: "true"
        baton-app: ninjio
    spec:
      containers:
      - name: baton-ninjio
        image: public.ecr.aws/conductorone/baton-ninjio:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-ninjio
        envFrom:
        - secretRef:
            name: baton-ninjio-secrets

Step 3: Deploy the connector

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

2. Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the NINJIO connector to. NINJIO data should be found on the Entitlements and Accounts tabs.

Done. Your NINJIO connector is now pulling access data into C1.

---

All versions of this connector are available at dist.conductorone.com.