AETERION

    Okta

    Okta integration

    IdentityAvailable

    BRAIAN connects to Okta through Okta API, API token. Agents can user and group sync, single sign-on and lifecycle events. Every action is scoped by the permissions granted to the integration and executed under a versioned policy. Each one is recorded in the audit log with the agent, timestamp and record touched.

    What can BRAIAN do?

    Users and groups are synchronised from Okta, single sign-on is handled by Okta itself and lifecycle events — joiners, movers, leavers — update what agents and Carol may reach.

    CapabilityAgentRead or write
    User and group syncAll agentsRead
    Single sign-onCarolRead
    Lifecycle eventsSecAgentRead

    How does it connect?

    Connection method
    Okta API, API token
    Credential
    An Okta API token issued to a service account and held in the secrets store.

    Credentials are held in an encrypted secrets store. BRAIAN never stores end-user passwords.

    Which permissions are required?

    • okta.users.readUser attributes needed to resolve identity.
    • okta.groups.readGroup membership, mapped to agent permissions.

    Permissions are requested at the minimum scope the configured processes require. Unused scopes are not granted.

    Which processes use it?

    Processes that run on this connection, and the domains they belong to.

    • Access certification

    • Data access review

    Used across every business domain.

    How do you revoke access?

    Access is revoked in Okta itself — by disabling the credential or removing the granted scopes — or in BRAIAN by disconnecting the integration. Processes already running stop at their next call to Okta and are held for review rather than completed with partial data; the interruption and the state of each process are recorded in the audit log.

    FAQ

    Does BRAIAN store data from Okta?

    BRAIAN reads what a process needs, when it needs it. Records retrieved from Okta are held only for the duration of the process and in the audit trail of the actions taken; Okta remains the system of record.

    What happens if the connection fails mid-process?

    The process stops at the failed step and is held for review. Nothing is written twice: completed writes stay recorded in the audit log and the remaining steps resume only once the connection is restored.

    Can permissions be scoped per agent?

    Yes. Scopes are defined per agent, not per system, so one agent can read while another cannot, on the same connection to Okta.