Expand description
Security scheme types for A2A agent authentication.
The individual scheme types follow the OpenAPI 3.x security model, which
A2A borrows their field sets from. The root discriminated union
SecurityScheme does not: in v1.0 it is a protobuf oneof, so it is
externally tagged on the wire ({"apiKeySecurityScheme": {…}}) rather than
internally tagged on a "type" field as it was in v0.3. Both encodings are
accepted; only the v1.0 one is emitted.
NamedSecuritySchemes is a type alias, and SecurityRequirement is a
struct used in crate::agent_card::AgentCard and
crate::agent_card::AgentSkill.
Structs§
- ApiKey
Security Scheme - API key security scheme: a token sent in a header, query parameter, or cookie.
- Authorization
Code Flow - OAuth 2.0 authorization code flow.
- Client
Credentials Flow - OAuth 2.0 client credentials flow.
- Device
Code Flow - OAuth 2.0 device authorization flow (RFC 8628).
- Http
Auth Security Scheme - HTTP authentication security scheme (Bearer, Basic, etc.).
- Implicit
Flow - OAuth 2.0 implicit flow (deprecated; retained for compatibility).
- Mutual
TlsSecurity Scheme - Mutual TLS security scheme.
- OAuth2
Security Scheme - OAuth 2.0 security scheme.
- Open
IdConnect Security Scheme - OpenID Connect security scheme.
- PasswordO
Auth Flow - OAuth 2.0 resource owner password credentials flow (deprecated but in spec).
- Security
Requirement - A security requirement object mapping scheme names to their required scopes.
- String
List - A list of strings used within a
SecurityRequirementmap value.
Enums§
- ApiKey
Location - Where an API key is placed in the request.
- OAuth
Flows - Available OAuth 2.0 flows for an
OAuth2SecurityScheme. - Security
Scheme - A security scheme supported by an agent.
Type Aliases§
- Named
Security Schemes - A map from security scheme name to its definition, as used in
AgentCard.securitySchemes.