The hook reads authdog_token from crew inputs, then removes that key before tasks render. The process that calls the token endpoint holds the client secret. This crew does not.
The exchange is in Agent frameworks.
Which credential
| Credential | Use it when |
|---|---|
| Agent identity | A named agent inside a project that already has users. Agents is sales-gated until access is approved. |
| M2M application | The caller is a job, or Agents access is not approved yet. Same client_credentials grant. |
| Personal access token | One person's script. Keep it off an unattended caller. |
| Service account | Authdog REST automation. Not the bearer this hook checks. |
To act for a person, keep this hook and present an RFC 8693 token. sub stays the user. act names the agent. The planned sample uses a token whose subject is the agent.
Related
| Read | To learn how to |
|---|---|
| Custom channel auth for CrewAI | Refuse a missing bearer |
| Machine identity | Choose the credential |
| CrewAI | See the hook |