Skip to content

Consolidate revocation logic to one spot #188

Closed

Description

@niilovuo

User story

As a rasenmaeher developer,

I want to have consolidated logic for certificate revocation checking,

to avoid repeating myself, and to prevent feature drift.

Acceptance Criteria

Outline what you think are requirements for this story to be considered Completed.

  • web/api/internal/callsign_validity.py removed, or appropriately made a simple wrapper for ocsp (depending on implementation details with middleware.)

Linked things

Link epics, features and other user stories here, if applicable.
https://pvarki.getoutline.com/doc/rasenmaeher-api-trustidentity-audit-OpE3XR3jBm

Activity

  1. self-assigned this
    on Sep 16, 2026
  2. niilovuo commented on Sep 18, 2026

    @niilovuo
    ContributorAuthor
  3. added
    product:platformCore product: the k8s native platform itself and its core services
    product:rasenmaeher-v2Core product: The new identity manager in OpenDefence platform - RM turned to k8s operator
    on Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

product:platformCore product: the k8s native platform itself and its core servicesproduct:rasenmaeher-v2Core product: The new identity manager in OpenDefence platform - RM turned to k8s operator

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions