Skip to main content
Connect Port with your organization’s Client ID and Client Secret to sync users and blueprints, 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 Port organization with their name, email, the names of the Port roles assigned to them (or Admin when a role is flagged as admin but unnamed, or Member when none), and the date they were created. Port’s own status is respected — a user Port reports as anything other than active is shown as Inactive. Port reports no MFA state, so the MFA column shows Unknown.
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 Port user roster — names, emails, roles, status and creation dates — which appears on your Access page; and your Port blueprints, which appear on your Inventory page with their title and description. Entities, scorecards and actions are not read.It calls these Port endpoints on api.getport.io (or api.us.getport.io for US-region organizations):
  • /v1/auth/access_token (exchanges the Client ID and Secret for a short-lived token)
  • /v1/users
  • /v1/blueprints
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Port environment.

​
Troubleshooting

The Client ID and Client Secret must be the pair from the Organization tab of your Port credentials, pasted into their own fields — the two values look alike. A wrong Region fails the same way: an organization on the US instance must be connected with us. Copy the pair again and connect again.
Port shows a client secret at creation and is phasing out re-displaying it. If you did not copy it, generate a new secret from the same Credentials page, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Port.
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.