Skip to content

[0.7] A2A cascade revocation #140

@Raulgooo

Description

@Raulgooo

Release

0.7 — A2A Auth Layer

Objective

Revoke A2A token → all downstream A2A calls fail.

Problem

  • A2A revocation doesn't cascade
  • Downstream calls succeed after upstream revoked

Fix

  1. POST /authority/revoke handles A2A tokens
  2. Mark revoked in graph
  3. Invalidate all downstream tokens
  4. Immediate effect

Files

  • internal/api/authority_handlers.go
  • internal/storage/delegation.go
  • internal/storage/tokens.go

Acceptance Criteria

  • A2A revocation cascades
  • Downstream calls fail immediately
  • Graph shows revoked status
  • Audit log
  • SDK: shark.authority.revokeA2A(id)

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Urgent: - major component broken - High importance vulnerability - Same daytrack-authorityTrack label for Agentic Era

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions