Skip to main content

​
About Jenkins

Iru calls the Jenkins remote API with HTTP Basic authentication: username plus an API token as the password (preferred over a real password). The wizard first stores jenkins_host (hostname and optional context path only), then collects credentials.

​
How It Works

Authorization: Basic base64(username:api_token)
DetailValue
CategoryCI/CD
AuthenticationBasic (user + API token)
Official references: Scripted clients, API tokens, Remote API.

​
Prerequisites

  • Jenkins reachable from Iru’s network (firewall / VPN / allowlist as needed).
  • A user with Overall/Read and job-level read access for the scope you audit.
  • HTTPS strongly recommended for the controller.

​
Connect Jenkins to Iru

Complete this tab before you connect the source in Compliance.
1

Sign in to Jenkins

Open your Jenkins controller URL and sign in with a user who has at least Overall/Read and the job read access your compliance scope needs.
2

Open your user profile

Click your username in the upper-right (or the People link, then your user), depending on your Jenkins theme.
3

Open Configure

Select Configure for your user account so you can edit personal settings.
4

Open the API Token section

Scroll to the API Token section (or API Token / Add new Token, depending on Jenkins version). If you do not see it, your administrator may restrict token creation.
5

Create a new token

Choose Add new Token, enter a name such as Iru Compliance, then select Generate (or Create). Copy the token once when Jenkins shows it.Optional expiry may apply; Jenkins also surfaces aging tokens in the UI so you can rotate before they lapse.
Continue on the Iru Compliance tab.

​
Troubleshooting

Check pop-up blocker settings for the Iru site and try again.
Toggle source off/on for a fresh wizard session.
Correct user/token; user needs read permissions on target jobs.
Routing, TLS, VPN, or allowlist for Iru egress.
Include context path if Jenkins is not at domain root.

​
Considerations

Use a read-only service user scoped to the folders…

Use a read-only service user scoped to the folders or views you need.

Sources Management

Browse and manage every Compliance source.

Getting Started With Compliance

Frameworks, actions, and Artifacts.

Iru Overview

How Endpoint, Compliance, and Identity fit together.

Artifacts Management

Upload, review, and organize evidence from sources and actions.