> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 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       | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Administrator | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Group         | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Repository    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

**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](https://jfrog.com/help/r/myjfrog-portal/create-an-api-token-in-myjfrog)

## Configure the Artifactory connector

<Warning>
  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
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Artifactory** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Artifactory 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
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Enter the configuration information from the previous section.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Artifactory connector is now pulling access data into C1.
  </Tab>

  <Tab title="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](mailto:support@c1.ai) to download the latest version of the connector.

    ### Step 1: Set up a new Artifactory connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Artifactory 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
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.
        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Artifactory connector deployment:

    #### Secrets configuration

    ```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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: ghcr.io/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

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        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.
      </Step>
    </Steps>

    **Done.** Your Artifactory connector is now pulling access data into C1.
  </Tab>
</Tabs>