Directory Console 0.4.0

Nothing changes until an administrator turns agent keys on for a directory (Settings > Directory > Agent keys): they are off by default. There's nothing to change in compose.yaml, and the configuration format is unchanged, so going back to 0.3.24 needs no restore. See UPGRADING.

AI agents over MCP

An AI agent can now work in the console as the person who gave it an agent key, through the console's MCP server at /mcp. It works with that person's own eDirectory rights, and at most the roles they give the key. See docs/MCP.md and the screenshots.

• Agent keys: a person makes a key under their name > Agent keys.
  • Confirming it's them: their password, or a recent single sign-on.
  • What it may do: reading always; changing objects or running Identity Manager only if they have those roles; never admin.
  • How long it lasts: 30 days by default (at most the directory's limit, 90 days at most, and 14 days with single sign-on); a key unused for 14 days stops.
  • Shown once, with the setup: the key appears once, with the command to add it to Claude Code. The console keeps only a hash, outside backups.
  • Revoking: a person can revoke their own keys at once, and administrators everyone's.
• Acting as the person: each call acts as the person through the service account, as single sign-on does.
  • The console refuses a key whose person is locked by intruder detection, disabled, expired or without a role, checked on every call.
  • Calls are audited with the key's label.
• Read tools: objects and search, groups, sign-in status, driver sets and drivers, jobs, the association, cache and object inspectors, statistics and versions.
• Change tools: enable, disable and unlock accounts; group membership; start and stop drivers; run and abort jobs; resynchronize; migrate. The key must have the role, reaching the object.
• Approval: a change an agent asks for waits until the person approves it in the console, typing the directory's name on production. They can also decline it, and it expires after an hour. An administrator can turn approval off per directory; then on production the agent passes the directory's name, typed by the person.
• Identity Applications: with its address set (Settings > Directory), a key made with a password also signs its person in to Identity Applications once, keeping only the refresh token.
  • Reads: their approval tasks and requests, who holds a role or resource, and assignments.
  • Changes: approve or deny tasks (with the approval form's fields), request PRDs, roles and resources, revoke roles and resources, and retract requests. These follow the same approval.

Also

• Single sign-on refuses an account locked by intruder detection. eDirectory accepts the proxied-authorization control for such an account, so this check is the console's own.
• Clearer refusals: account changes and unlock report "insufficient rights" where eDirectory answered "no such attribute" under proxied authorization.
• Updated core: built on DirXMLDev 0.60.0, which carries the Identity Applications client.

Before you use agents

• Behind a reverse proxy: forward /mcp, with its Authorization header (DEPLOYING).
• Certificates: the agent's machine must trust the console's certificate. With the console's own certificate, start Claude Code with NODE_EXTRA_CA_CERTS pointing to a copy of it.
• Restarts: changes waiting for approval are kept in memory, so a restart drops them, and the agent asks again.