Skip to main content
Connect Aiven with a personal API token to sync organization users, projects and services, 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 the human users of one Aiven organization — the one with the lowest organization ID among those the token can see — with their name, email, whether they are a Super Admin or a Member, whether they are managed by SCIM, the date they joined, and Aiven’s own active or inactive state. Application users (Aiven’s machine accounts) are left out. Aiven reports no MFA state on this endpoint, 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 Aiven organization user roster — names, emails, super-admin status, SCIM management, join dates and account state — which appears on your Access page; and your Aiven projects and the services inside them, which appear on your Inventory page with their cloud, tier, service type, plan and state.It calls these Aiven endpoints:
  • /v1/me
  • /v1/organizations
  • /v1/organization/{id}/user
  • /v1/project
  • /v1/project/{name}/service
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Aiven environment.

​
Troubleshooting

A personal token inherits the permissions of the user who created it, and among the organizations that token can see, DSALTA syncs the one with the lowest organization ID. Create the token as an organization admin who belongs to the organization you want reviewed. If your admin belongs to several organizations, create the token from a user who belongs only to the one you want.
Aiven tokens carry a session duration chosen at creation, and an organization can enforce an authentication policy that limits personal tokens. Generate a new token, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from Aiven.
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.