Set up a Sonatype Nexus connector

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

Capabilities

Resource	Sync	Provision
Accounts
Roles

The Nexus connector supports automatic account provisioning and deprovisioning. All accounts must be assigned at least one role; new accounts will automatically be assigned the nx-anonymous role on creation.

When a new account is created by C1, the account’s password will be sent to a vault.

Gather Nexus credentials

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

1. The username and password for your Nexus account, or for a service account you’ve set up.

   Make sure the account used to configure the connector has the relevant permissions:

   • To sync (read) users and roles: Read access to users and roles

   • To provision (read-write) users and roles: Read and write access to users, roles, and user-role assignments

2. The host URL of your Nexus instance (for example: https://nexus.company.com).

Done. Next, move on to the connector configuration instructions.

Configure the Nexus connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Nexus credentials generated by following the instructions above

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 Nexus and click Add.

3. Choose how to set up the new Nexus 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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. Enter the Nexus credentials into the relevant fields.

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

Self-hosted

**Follow these instructions to use the Nexus 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. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Nexus 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 Nexus 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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 Nexus connector deployment:

Secrets configuration

# baton-sonatype-nexus-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sonatype-nexus-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Nexus credentials
  BATON_USERNAME: <Nexus account username>
  BATON_PASSWORD: <Nexus account password>
  BATON_HOST: <Nexus tenant URL>

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

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