Skip to content

Configuring the Jenkins SaaS Connector

To connect Jenkins to Agentic Fabric, you'll create an API token for Jenkins. This will allow Agentic Fabric to discover credentials, pipelines, and managed controllers and aggregate them as non-human identities.

Important

If your organization has already configured a Jenkins SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

Creating an API Token in Jenkins

You must have administrative privileges to manage users in Jenkins.

  1. Create a new Jenkins user (user account). SailPoint recommends creating a dedicated service account for this integration.
  2. Create an API token for the account approved for the integration.
  3. Copy the API token. You'll provide the token to connect Jenkins to Agentic Fabric.
  4. Grant the account the read access your governance program requires. Exact permissions depend on your authorization model. Your platform team should align on the datasets you enable.

Note

If your deployment uses a central Operations Center entry point and separate managed controllers, confirm with your administrators that the same integration identity is valid for all targets the connector must reach.

Connecting Jenkins to Agentic Fabric

  1. Go to the Connect Source step of the Agentic Fabric onboarding experience.
  2. Select Jenkins SaaS from the left pane.

  3. In the Jenkins SaaS section, complete the following:

    • In the Source Name field, enter a unique name for the source.

    • In the Source Owner field, select the identity who will own the source.

    • In the Description field, enter a unique description for the source to distinguish it from similar connections.

  4. In the Configure Authentication section, complete the following:

    • In the Jenkins URL field, enter the base URL of the Jenkins environment used for API access. Do not include the Operations Center context path in this field.
    • Enable the OpenSource Jenkins toggle if your organization uses a standalone open-source Jenkins instance.
    • If your organization uses CloudBees Jenkins Operations Center deployment, enter the single path segment for the Operations Center servlet context in the Operational Center Context Path field. Do not enter a full URL.
    • In the User ID field, enter the User ID for the Jenkins user (user account) used for the integration. You can find a list of user IDs by going to Manage Jenkins > Users in Jenkins.
    • In the API Token field, paste the API token you created.

  5. Select Test Connection to ensure the connection is successful.

  6. If the test is successful, select Aggregate to run an aggregation for the source. Select Exit to skip this step. You can configure aggregations for the source's datasets later in the source's configuration. For information about datasets specific to Jenkins, refer to the Jenkins connector documentation.

    A Completed status is now displayed next to the source in the left panel.

  7. Choose another connector to configure or select Continue to proceed to the next onboarding step.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.