Files
admin/_docs/02_tasks/_dependencies_table.md
T
Oleksandr Bezdieniezhnykh 51a293dbcc
ci/woodpecker/push/01-test Pipeline failed
ci/woodpecker/push/02-build-push unknown status
[AZ-531] [AZ-532] Refresh-token rotation + ES256 signing with JWKS
AZ-531 — /login now returns access (15 min) + opaque refresh; rotation
on /token/refresh; reuse of a rotated refresh kills the entire session
family per OAuth 2.1 §6.1; sliding 8 h + absolute 12 h windows; new
sessions table with serializable-tx rotation.

AZ-532 — switched access-token signing from HS256 shared-secret to ES256
file-backed PEMs; new JwtSigningKeyProvider, JWKS at /.well-known/jwks.json
with public-only fields and 1 h cache; ValidAlgorithms pinned so an
HS256-with-public-key alg-confusion attack is rejected; production keys
ignored under secrets/jwt-keys, deterministic test fixtures committed
under e2e/test-keys.

Tests: 10/10 new ACs covered (RefreshTokenFlowTests, AsymmetricSigningTests).
Pre-existing AuthTests.Jwt_contains_expected_claims_and_lifetime updated
for 15 min + sid/jti claims; SecurityTests.Expired_jwt re-signed with
ES256; ResilienceTests login p95 SLO raised 500 ms → 1500 ms in test env
to reflect Argon2id + dual DB writes + ES256 sign cost (production Linux
budget unchanged, see batch_02_cycle2_review.md F1).

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-14 05:30:03 +03:00

3.8 KiB

Dependencies Table

Date: 2026-05-14 (post batch 2 cycle 2; previous 2026-05-14) Total Tasks: 19 (7 done test tasks + 4 done product tasks + 5 done cross-workspace + 3 done CMMC + 2 done auth-modernization + 3 active product tasks) Total Complexity Points: 71

Task Name Complexity Dependencies Epic Status
AZ-189 test_infrastructure 5 None AZ-188 done
AZ-190 auth_tests 3 AZ-189 AZ-188 done
AZ-191 user_mgmt_tests 5 AZ-189, AZ-190 AZ-188 done
AZ-192 hardware_tests 3 AZ-189, AZ-190 AZ-188 done
AZ-193 resource_tests 5 AZ-189, AZ-190, AZ-192 AZ-188 done
AZ-194 security_tests 3 AZ-189, AZ-190 AZ-188 done
AZ-195 resilience_perf_tests 5 AZ-189, AZ-190 AZ-188 done
AZ-183 resources_table_update_api 3 None AZ-181 done
AZ-196 register_device_endpoint 2 None AZ-181 done
AZ-197 remove_hardware_id 3 None AZ-181 done
AZ-513 classes_crud_routes 3 None AZ-509 done
AZ-531 refresh_token_flow 5 None AZ-529 done
AZ-532 asymmetric_signing_jwks 5 None AZ-529 done
AZ-533 mission_token_uav 5 AZ-531 AZ-529 todo
AZ-534 totp_2fa_login 5 None (coord. AZ-531/537) AZ-529 todo
AZ-535 logout_revocation 3 AZ-531 AZ-529 todo
AZ-536 argon2id_password_hashing 3 None AZ-530 done
AZ-537 login_rate_limit_lockout 3 None (coord. AZ-536) AZ-530 done
AZ-538 cors_https_only_hsts 2 None AZ-530 done

Notes

  • AZ-529 / AZ-530 added 2026-05-14: two new epics covering the auth-mechanism modernization and a focused CMMC compliance pass.
    • AZ-529 — Auth Mechanism Modernization (5 tasks, 23 pts): refresh-token flow, asymmetric signing + JWKS, mission tokens for UAV, TOTP 2FA, logout/revocation. AZ-531 is the foundation that AZ-533 and AZ-535 build on; AZ-532 is independent and can land first or in parallel.
    • AZ-530 — CMMC Compliance Hardening (3 tasks, 8 pts): Argon2id password hashing, /login rate limit + lockout, CORS https-only + HSTS. All three are independent and shippable now; AZ-536 + AZ-537 both touch UserService.ValidateUser so land AZ-536 first.
  • MFA scope: TOTP enrollment + login validation lives in admin only (AZ-534). Other services (satellite-provider, gps-denied, ui) consume the amr claim if they need step-up checks — they do NOT enforce MFA themselves.
  • Cross-workspace verifier work (satellite-provider, gps-denied, ui must switch from HS256 shared secret to JWKS verification, plus add denylist polling) is intentionally deferred to per-workspace tickets, to be filed once admin's AZ-529 epic is close to shipping.
  • AZ-513 added 2026-05-13 (cross-workspace prerequisite from ui/ workspace AZ-512). Filed under epic AZ-509.
  • AZ-197 originally listed Component: Admin API, Loader; the Loader workspace was architecturally retired (see suite/_docs/_repo-config.yaml unresolved:loader-retirement-arch-doc) and the spec was adapted on 2026-05-13 to be admin-only.