Skip to content

fixes #3680 add revocation management API, CLI, and enforcement#3789

Draft
andrewpmartinez wants to merge 2 commits intomainfrom
fix.openziti.ziti.3680.revocation-management-api
Draft

fixes #3680 add revocation management API, CLI, and enforcement#3789
andrewpmartinez wants to merge 2 commits intomainfrom
fix.openziti.ziti.3680.revocation-management-api

Conversation

@andrewpmartinez
Copy link
Copy Markdown
Member

@andrewpmartinez andrewpmartinez commented Apr 8, 2026

  • adds Management API endpoints for revocations (POST, GET, LIST) with type-aware validation (JTI/API_SESSION require UUID, IDENTITY requires existing identity)
  • adds CLI commands: ziti edge create revocation identity|api-session|jti
  • adds revocation checks to resolveOidcSession in security_ctx.go so the REST API returns 401 for revoked OIDC tokens. Previously only ValidateAccessToken (router ctrl channel path) checked revocations, so revoked tokens still received 200 OK from the management and client HTTP APIs
  • adds api-session revocation check to ValidateAccessToken, which only checked JTI and identity revocations
  • adds Type field to Revocation model, store, and protobuf message
  • adds integration tests covering CRUD, input validation, and token enforcement for all three revocation types

Note: Relies on openziti/edge-api#184 and has commit hash specific deps that need to be resolved before merging.

@andrewpmartinez andrewpmartinez force-pushed the fix.openziti.ziti.3680.revocation-management-api branch 3 times, most recently from 5cd8641 to 9ed798c Compare April 8, 2026 21:18
- adds Management API endpoints for revocations (POST, GET, LIST) with
  type-aware validation (JTI/API_SESSION require UUID, IDENTITY requires
  existing identity)
- adds CLI commands: ziti edge create revocation identity|api-session|jti
- adds revocation checks to resolveOidcSession in security_ctx.go so the
  REST API returns 401 for revoked OIDC tokens. Previously only
  ValidateAccessToken (router ctrl channel path) checked revocations,
  so revoked tokens still received 200 OK from the management and client
  HTTP APIs
- adds api-session revocation check to ValidateAccessToken, which only
  checked JTI and identity revocations
- adds Type field to Revocation model, store, and protobuf message
- adds integration tests covering CRUD, input validation, and token
  enforcement for all three revocation types

use working edge-api branch name

update ref
@andrewpmartinez andrewpmartinez force-pushed the fix.openziti.ziti.3680.revocation-management-api branch from 9ed798c to 5f734d4 Compare April 8, 2026 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant