Set up a Boomi connector

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

Capabilities

Resource	Sync	Provision
Accounts
Roles
Account groups

Additional functionality: The Boomi connector supports automatic account provisioning.

Notes:

• The Boomi connector supports account provisioning and role assignment/revocation.
• Account deprovisioning (deleting users) is not supported. When revoking a user’s last role, the connector automatically assigns the “Standard User” role first to prevent accidental user deletion from the account.
• Users are created in Boomi by assigning them a role. New users receive an email invitation to complete their account setup.
• Account Groups are only available for Primary accounts that manage multiple sub-accounts. If your account is not a Primary account, the Account Groups sync will return empty results.
• Some global Boomi roles with non-standard UUID formats cannot be assigned via the API and are automatically excluded from assignable entitlements.

Understanding roles in Boomi

Boomi uses two types of role assignments:

Global Roles: Assigned to users at the account level, granting permissions across the entire Boomi account. These are managed through the Roles resource in ConductorOne.

Group Roles: When a user is added to an Account Group, they are assigned one or more specific roles within that group context. These are not roles that belong to the group itself, but rather roles that a specific user has within the context of that group. A single user can have multiple different roles within the same group. Each user-group-role combination is represented as a separate grant in ConductorOne under the Account Groups resource type.

Gather Boomi credentials

To configure the Boomi connector, you need at least Account Administrator role or equivalent permissions in Boomi to manage users, roles, and groups across the account. Additionally, your user must have the API Access privilege and the API Token feature enabled.

1. Log in to Boomi AtomSphere and navigate to Settings > My User Settings > User Information.

   Copy your email address from this page. You’ll need it in the next section.

   The connector will automatically format your email as BOOMI_TOKEN.{email} for API authentication, so you only need to provide your email address.

2. Navigate to Settings > My User Settings > Platform API Tokens.

   Click Add New Token.

3. 1. Enter a unique name for the token, such as ConductorOne
   2. Click Generate Token
   3. Copy the token and save it securely. You won’t be able to view it again after closing the dialog.

   You can generate up to five tokens per user account. Tokens inherit the permissions of the user who created them, so ensure your account has the necessary administrative privileges.

4. Navigate to Settings > Account Information and Setup.

   Copy your Boomi Account ID from this page. You’ll need it in the next section.

For more information about Boomi API tokens, see the Platform API Tokens documentation.

Configure the Boomi connector

Cloud-hosted

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

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for Boomi and click Add.

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

5. Click Next.

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

7. Paste the email address, API token, and Account ID into the relevant fields:

   • Boomi Email: Enter the email address you copied from your Boomi user settings
   • Boomi API Token: Paste the API token you generated earlier
   • Boomi Account ID: Enter your Boomi Account ID
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.

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

Self-hosted

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

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

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

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. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Boomi connector deployment:

Secrets configuration

# baton-boomi-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-boomi-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Boomi credentials
  BATON_BOOMI_EMAIL: <Your Boomi email address>
  BATON_BOOMI_API_TOKEN: <Your Boomi API token>
  BATON_BOOMI_ACCOUNT_ID: <Your Boomi Account ID>

  # 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-boomi.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-boomi
  labels:
    app: baton-boomi
spec:
  selector:
    matchLabels:
      app: baton-boomi
  template:
    metadata:
      labels:
        app: baton-boomi
        baton: true
        baton-app: boomi
    spec:
      containers:
      - name: baton-boomi
        image: ghcr.io/conductorone/baton-boomi:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-boomi
        envFrom:
        - secretRef:
            name: baton-boomi-secrets

Step 3: Deploy the connector

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

2. 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 Boomi connector to. Boomi data should be found on the Entitlements and Accounts tabs.

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