# How to map AI agents and humans to one identity model with OIDC

DevFeed: [How to map AI agents and humans to one identity model with OIDC](<https://devfeed.tech/articles/how-to-map-ai-agents-and-humans-to-one-identity-model-with-oidc-121569.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/05/how-to-map-ai-agents-and-humans-to-one-identity-model-with-oidc/>)

Author: Ritesh Patel

Published: 2026-11-05T07:00:00Z

Content type: tutorial

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Unified Access](<https://devfeed.tech/topics/unified-access.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [client](<https://devfeed.tech/tags/client.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [identity](<https://devfeed.tech/tags/identity.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [map](<https://devfeed.tech/tags/map.md>), [model](<https://devfeed.tech/tags/model.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [one](<https://devfeed.tech/tags/one.md>), [people](<https://devfeed.tech/tags/people.md>), [records](<https://devfeed.tech/tags/records.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [sso](<https://devfeed.tech/tags/sso.md>), [with](<https://devfeed.tech/tags/with.md>)

## AI overview

One OIDC issuer can serve people and delegated AI agents; Kubernetes trusts the issuer and maps token claims to usernames and groups. The guide's Entra example registers each agent as a separate client, pins the audience to its client ID, checks the tenant claim, and maps a stable claim such as `sub` or `oid` to the Kubernetes username. In delegated sessions, `sub` identifies the person per application, so record the agent client separately and include the delegating person in the audit trail only if the provider supplies a suitable claim. Key limits: Entra omits the groups claim above 200 groups, unattended app-only agents are outside the guide's scope, and Kubernetes authentication configuration cannot be combined with `--oidc-*` flags. Kubernetes accepts OIDC tokens but does not issue OIDC tokens for agents.

## Source excerpt

Put AI agents and people behind one OIDC issuer, register each agent as its own client, and map claims to the username your Kubernetes API server records for delegated sessions.