fix(liquio): build valid Cabinet JWTs and fail closed #199
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "hex-73/liquio-jwt-tooling-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Minimal native JWT repair authored by Adrian, original candidate 0eb8181ca9124ecb6d129234cc38ff125ec4e5c0 plus diagnostic stage markers. Exact complete production/test blobs retained. Explicit openssl dependency, fail-closed base64 output and non-empty JWT segments. Existing credential reuse, role and ownership behavior unchanged. Operator tests: four focused Helm/pytest passed; exact shell/JWT block with jq+openssl makes valid JSON and Python-verified HMAC, unavailable OpenSSL exits1 with no token. No new technical leader review; prior independent legacy-reuse approval remains limited to unchanged bytes. No extra review required for this bounded dependency/fail-closed correction under the current KISS contract.
Evidence: https://hex.local.samaschke.de/api/attachments/15094424-61e0-40e9-b5de-c97b80d118ce/content . Hosted CI unavailable (no workflows); not green. Normal pinned-head merge, no policy overrides. Publication, rollout and business acceptance are distinct.