BoundaryKit
Cookbook

Expire a session

Use expire a session in a scoped workspace and verify the result with alerts records.

Expire a session — confirm that a fresh request using the old session is denied.

Expire a session

Confirm that a fresh request using the old session is denied. Use a staging organization with the same grants as production. Keep the previous manifest digest available until the first production receipt has been inspected.

Capture the baseline

curl --fail-with-body "https://api.boundarykit.com/v2/alerts" -H "X-API-Key: $BKIT_KEY" -H "X-Organization-Id: $BKIT_ORG"

Apply to a single workspace

Use the following checkpoint while the staging change is isolated.

{
  "case": "expire-a-session",
  "organization": "org_stage",
  "revision": "rev_31",
  "checkpoint": "Confirm that a fresh request using the old session is denied."
}

Rollback condition

Inspect the receipt for Expire a session. Compare its organization and revision with the values in the fixture before interpreting the result. Restore the preceding manifest if a previously denied capability becomes available.