Single sign-on for agents
Single sign-on lets one sign-in, through a central identity provider, give access to many systems. For AI agents, the agent signs in as itself and reaches each system through that one identity, not a separate key per system.
In a run
The agent signs in as itself at the start of the job and gets one credential for that job. That credential lets it through to each service behind Ares in the run, such as the ERP, the mailbox and the document store. It expires with the job.
Our word for it
Each agent signs in as itself.
Why a key for each system goes wrong
An agent that holds its own password or key for each system carries long-lived secrets, and each one has to be tracked, rotated and revoked on its own. On Ares, one credential per job takes their place: see scoped credential. Decommissioning the agent stops all of its credentials.
People and agents, side by side
People sign in to Ares with the accounts they already have in your directory. Agents are enrolled with their own identities from the same directory, and no agent shares an account with a person or with another agent. The record keeps the two apart: the person who started the job, and the agent that acted.
Where it stops
- It covers the services the agent reaches through Ares. A system the agent reaches some other way is outside the credential and outside the record.
- See identity provider for which directories work today.
Security and data handling sets out where data goes and what is recorded.
Related terms
- Identity providerAn identity provider is the service that signs people in to other systems, using the accounts and groups in your directory.
- Scoped credentialA scoped credential covers a named set of actions for a limited time, instead of everything an account can do.
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.