Skip to main content
Connect Harness with a personal API token to sync account users and projects, and run access reviews. Read-only.
Read-only access. DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
What you’ll see. The Access page lists every user of your Harness account with their name, email and the names of the roles Harness reports for them, whatever scope those assignments are at, or Member when none. A user Harness reports as locked or disabled is shown as Inactive, with that state noted beside the role, and users managed through SCIM are marked (SCIM). Harness does report per-user two-factor authentication, so the MFA column shows Yes or No, and Unknown for a user whose two-factor state Harness omits. The MFA check counts an omitted state as not enabled. Harness reports no join date, so each row is stamped with the date of the sync.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Harness account user roster — names, emails, role assignments, locked and disabled state, SCIM management and two-factor state — which appears on your Access page; and your Harness projects, which appear on your Inventory page with their organization and enabled modules. Pipelines and executions are not read.It calls these Harness endpoints on app.harness.io, always with the account identifier taken from your token:
  • /ng/api/user/currentUser (used to validate the token)
  • /ng/api/user/aggregate (a POST that Harness uses to list users with their roles)
  • /ng/api/projects
Every request is a read of your account’s configuration. DSALTA has no code path that creates, modifies, or deletes anything in your Harness environment.

​
Troubleshooting

The token must be in the four-part form pat.<accountId>.<keyId>.<secret> — DSALTA reads the account identifier from the second segment, so a truncated token is rejected. Expired tokens fail the same way: create a new token and connect again.
A personal token inherits the permissions of the user who created it. Create it as a user whose account-level role can view users, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Harness.
Open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Manage on the integration’s card. Open the Status tab: it shows either Connected and working properly or Connection issues detected.Use the Status tab, not Overview — Overview always reports Connected regardless of the real state.
On an integration-powered check, Failed normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to Source Data, and read the result code: 403 is a missing permission, 428 is a setting DSALTA still needs, 500 is a failure on DSALTA’s side.A real compliance gap shows 207 and leaves the test looking Completed. See Understanding Test Results.
Compliance checks re-run once a day at 02:00 America/New_York. To refresh sooner, open Integrations → Connected and click Sync from integrations at the top right — it refreshes every connected integration at once.
There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.
Disconnecting is destructive and cannot be undone. DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see Integration errors.
That is expected. Configure scope is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.