> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Neo4j Aura

> Graph database — members & access

<Tabs>
  <Tab title="Overview">
    Connect Neo4j Aura with API client credentials to sync organization members, database instances, and the activity feed, and run access reviews. Read-only.

    <Info>
      **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.
    </Info>

    <Note>
      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.
    </Note>

    ## What DSALTA reads

    DSALTA reads your Aura organization members — email address, organization roles with per-project roles merged in, and per-user MFA enrollment status — which appear on your **Access** page; your Aura instances, with type, memory, storage, region, cloud provider and status, which appear on your **Inventory** page; and the organization activity feed — actor email, source IP, action name and outcome — which appears on your **Changes** page. Aura's member record carries no display name and no join date, so the **Access** page shows the email in the name column, and members who sign in through an external identity provider read `Unknown` for MFA. Reading the member list requires a credential created by an Organization Owner or Admin. This integration covers Aura, Neo4j's managed cloud; self-hosted Neo4j keeps its users inside the database and cannot be connected here.

    It calls these Neo4j Aura endpoints:

    * `POST /oauth/token`
    * `/v2beta1/organizations`
    * `/v2beta1/organizations/{org}/users`
    * `/v2beta1/organizations/{org}/projects`
    * `/v2beta1/organizations/{org}/projects/{project}/users`
    * `/v2beta1/organizations/{org}/activity-feed`
    * `/v1/instances`
    * `/v1/instances/{id}`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Neo4j Aura environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection fails to validate">
        Could not authenticate. Check the Client ID and Client Secret, and that the credential belongs to an Organization Owner or Admin.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        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.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        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](/guides/data-library/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        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.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **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](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        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.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    A Neo4j Aura Client ID and Client Secret, exchanged for a bearer token over OAuth2 client credentials. Read-only.

    **Before you begin**

    * A Neo4j Aura account with at least one project
    * Organization Owner or Admin role — the credential inherits the roles of the person who creates it, and reading the member list requires organization-level access

    You will need:

    | Field             | Where to find it    | Example                                          |
    | ----------------- | ------------------- | ------------------------------------------------ |
    | **Client ID**     | See the steps below | `iidhFHfb2jeQdiyGYCv7yomYhtiFx7z7`               |
    | **Client Secret** | See the steps below | `Shown only once when the credential is created` |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Neo4j Aura**, and click **Connect** to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
      </Step>

      <Step title="Open Account settings in the Aura Console">
        Sign in at console.neo4j.io as an Organization Owner or Admin. Click your avatar in the top-right corner, then choose Account settings.
      </Step>

      <Step title="Open the Client credentials tab">
        On the Account settings page, switch from the General tab to the Client credentials tab.

        <Tip>
          Neo4j's documentation refers to this as **My Profile → API Keys**. In the current console it is **Account settings → Client credentials**.
        </Tip>

        <img src="https://mintcdn.com/dsalta/vro64-iXPcheSKPf/images/integrations/neo4j-aura/01-client-credentials-tab.png?fit=max&auto=format&n=vro64-iXPcheSKPf&q=85&s=d1a7cec4247fa870a268b5df5064acd1" alt="Neo4j Aura's Account settings page with the Client credentials tab selected and the Aura API sub-tab active, showing the Create client credential button above a table of existing credentials with their Name, Client ID and Created At columns" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="1462" height="635" data-path="images/integrations/neo4j-aura/01-client-credentials-tab.png" />
      </Step>

      <Step title="Create a credential">
        Click Create, give it a name such as DSALTA, and confirm. Aura shows the Client ID and Client Secret once, in a single dialog — copy both now.

        <Tip>
          If you lose the secret you cannot view it again. There is no reveal action and no rotate action: delete the credential and create a new one, then reconnect with the new pair.
        </Tip>
      </Step>

      <Step title="Connect Neo4j Aura">
        Paste the Client ID and Client Secret you just copied, then click Connect.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the credential when you click **Connect** — it exchanges the Client ID and Secret for a token and reads your organization before saving anything. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** Could not authenticate. Check the Client ID and Client Secret, and that the credential belongs to an Organization Owner or Admin.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check                                                                                                                     | Severity | What it verifies                                                                              |
    | ------------------------------------------------------------------------------------------------------------------------- | -------- | --------------------------------------------------------------------------------------------- |
    | [User access to Critical System should be valid](/integrations/neo4j-aura/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Neo4j Aura access is an active employee on the People page.         |
    | [Offboarded users should not have active access](/integrations/neo4j-aura/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Neo4j Aura access.                     |
    | [MFA should be enabled for all users](/integrations/neo4j-aura/mfa-enabled-for-all-users)                                 | High     | Checks that every Neo4j Aura organization member has enrolled in multi-factor authentication. |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                      |
    | ------- | ----------------------------------------------------------------------------------------- |
    | Setup   | [Neo4j Aura API authentication](https://neo4j.com/docs/aura/platform/api/authentication/) |
    | Setup   | [Neo4j Aura Console](https://console.neo4j.io)                                            |
    | General | [Neo4j website](https://neo4j.com)                                                        |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)                   |
  </Tab>
</Tabs>