Set up a JFrog Artifactory connector

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

Capabilities

Resource	Sync	Provision
Account
Administrator
Group
Repository

Additional functionality:

• Create user accounts — Provision new Artifactory users with a randomly generated password.
• Delete user accounts — Remove users from Artifactory.
• Grant/revoke Administrator role — Assign or remove the platform admin flag on a user.
• Grant/revoke group membership — Add or remove users from Artifactory groups.
• Grant/revoke repository permissions — Manage per-repository permissions (Read, Write, Delete, Manage, Annotate, Managed Xray Metadata) for both users and groups. Permissions are managed via baton-owned permission targets.

Known limitations:

• Repository permissions granted via pre-existing Artifactory permission targets (not created by C1) cannot be revoked through this connector. Only permissions provisioned by C1 can be revoked.
• When a user inherits a repository permission from multiple groups, the connector attributes the grant to one group.

Gather Artifactory configuration information

Configuring the connector requires you to pass in information from Artifactory. Gather these configuration details before you move on.

Here’s the information you’ll need:

• Base URL
• Reference Token

See the Artifactory docs for information on how to acquire credentials: View the documentation

Configure the Artifactory connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Artifactory configuration information gathered 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 Apps > Connectors and click Add connector.

2. Search for Artifactory and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. Enter the configuration information from the previous section.

9. Click Save.

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

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

Self-hosted

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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Artifactory connector

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

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. 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 Artifactory connector deployment:

Secrets configuration

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

  # Artifactory config
  BATON_ARTIFACTORY_BASE_URL: <Base URL for artifactory>
  BATON_ARTIFACTORY_REFERENCE_TOKEN: <Reference token for artifactory>

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

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