POST /auth/refresh — rotation (R26) va reuse detection (UC9)

team-lead-ep-09 yangiladi

Yangilandi: pr_url

team-lead-ep-09 bog'liqlik qo'shdi

→ EP-09-T03-S01

team-lead-ep-09 yangiladi

Yangilandi: estimate_hours

qa-ep-09-t03-s04 statusni o'zgartirdi Review → Bajarildi

qa-ep-09-t03-s04 izoh qoldirdi

QA PASS. Spec: 09_auth.md #8 UC9 + R26 (qator 3125-3151) + section 2.3c (qator 469-527) kod bilan solishtirildi, mos. Test: flock ostida mvn -Dtest=RefreshServiceIntegrationTest -> 6/6 yashil (Testcontainers PG16). AC703-707 alohida tekshirildi: (1) UserSessionRepository.markRotated/rotate -- revoked_reason literal 'rotated' (V6 CHECK 9 qiymat mos), session_family_id/audience server-tomonda INSERT..SELECT bilan ko'chadi. (2) RefreshService.refresh() reuse branch -- revokeFamily + markTokenInvalidFrom + auth_logs, 401 generic. (3) revokeFamily WHERE session_family_id=:fid AND revoked_at IS NULL -- boshqa oila tegilmaydi. (4) AC706 countOpenSessionsForFamily testda tekshirilgan. (5) RefreshAuditLogger.logTokenReuseDetected -> auth_logs INSERT. MUTATSIYA TEKSHIRUVI (3 ta, har safar git checkout bilan qaytarildi): revoked_reason 'rotated'->'logout' => AC703 testi yiqildi (kutilganidek); revokeFamily dan session_family_id filtrini olib tashlash => AC705 testi yiqildi; Transactional(noRollbackFor=UnauthorizedException.class) ni olib tashlash => AC704 testi yiqildi (revocation+audit rollback bo'lib ketdi) -- bu eng qimmatli himoya, tasdiqlandi. Hash algoritmi: RefreshTokenHasher SHA-256 (BCrypt emas) -- spec #2.3c/UC9 aniq algoritm ko'rsatmagan, faqat UNIQUE tenglik qidiruvi talab qiladi (R26/2.3c indeks jadvali) -- BCrypt tasodifiy salt bilan bu ishlamaydi, muhandislik qarori spec bilan ziddiyatsiz, DEFEKT EMAS. UserRepository.markTokenInvalidFrom() -- S03 workeri tomonidan qo'shilgani tasdiqlandi (fayl mavjud, ishlaydi). Kontrakt: openapi/v1/auth.yaml (boshqa parallel agent tomonidan staged, T00) -- /auth/refresh RefreshRequest/RefreshResponse maydon nomlari va 401 ErrorResponse{code,message,request_id} kod bilan aynan mos. Cross-cutting: Transactional to'g'ri (yozuv, noRollbackFor asosli); tenant_id yo'q (AR-1); FK/katalog aloqasi yo'q shu bargda; outbox/broker ishlatilmagan (sync, R55 b); nomlash snake_case mos; precision N/A; soft-delete o'rniga revoked_at (spec dizayni, to'g'ri); parol/token log'ga yozilmaydi (RefreshAuditLogger faqat actor_type/user_id/action/result/error_code/ip/user_agent/request_id).

qa-ep-09-t03-s04 qabul mezonini belgiladi

✓ `auth_logs` da `token_reuse_detected`/`deny` qatori yoziladi

qa-ep-09-t03-s04 qabul mezonini belgiladi

✓ Ochiq sessiyalar ro'yxati (`revoked_at IS NULL`) `rotated` qatorlarni ko'rsatmaydi

qa-ep-09-t03-s04 qabul mezonini belgiladi

✓ Reuse'da BOSHQA `session_family_id` dagi sessiyalar tirik qoladi (E19)

qa-ep-09-t03-s04 qabul mezonini belgiladi

✓ Rotatsiya qilingan (eski) refresh token bilan kelinsa: butun oila `reuse_detected` bilan bekor bo'ladi, `token_valid_after` qo'yiladi, javob `401` — AC17

qa-ep-09-t03-s04 qabul mezonini belgiladi

✓ Refresh'dan keyin eski qator `revoked_reason='rotated'` bo'ladi (`logout` EMAS), yangi qatorda o'sha `session_family_id` va o'sha `audience`

coder-ep-09-t03-s04 statusni o'zgartirdi Ishlanyapti → Review

Test yashil: RefreshServiceIntegrationTest 6/6 (sinxron, flock ostida ikki marta tasdiqlangan). 5/5 acceptance criteria bajarilgan. Muhim texnik topilma: @Transactional(noRollbackFor = UnauthorizedException.class) shart edi — aks holda reuse holatidagi revoke/audit yozuvlari 401 javob bilan birga avtomatik rollback bo'lib ketardi.

coder-ep-09-t03-s04 yangiladi

Yangilandi: branch, commit_sha

coder-ep-09-t03-s04 qabul mezonini belgiladi

✓ `auth_logs` da `token_reuse_detected`/`deny` qatori yoziladi

coder-ep-09-t03-s04 qabul mezonini belgiladi

✓ Ochiq sessiyalar ro'yxati (`revoked_at IS NULL`) `rotated` qatorlarni ko'rsatmaydi

coder-ep-09-t03-s04 qabul mezonini belgiladi

✓ Reuse'da BOSHQA `session_family_id` dagi sessiyalar tirik qoladi (E19)

coder-ep-09-t03-s04 qabul mezonini belgiladi

✓ Rotatsiya qilingan (eski) refresh token bilan kelinsa: butun oila `reuse_detected` bilan bekor bo'ladi, `token_valid_after` qo'yiladi, javob `401` — AC17

coder-ep-09-t03-s04 qabul mezonini belgiladi

✓ Refresh'dan keyin eski qator `revoked_reason='rotated'` bo'ladi (`logout` EMAS), yangi qatorda o'sha `session_family_id` va o'sha `audience`

coder-ep-09-t03-s04 izoh qoldirdi

Texnik qarorlar: (1) Refresh token xeshi — SHA-256 (hex), BCrypt EMAS: UNIQUE(refresh_token_hash) bo'yicha tenglik qidiruv kerak, BCrypt tasodifiy salt bilan buni imkonsiz qiladi (spec aniq algoritm ko'rsatmagan — RefreshTokenHasher javadoc'ida asoslangan; login S02 ham shu servisdan foydalanishi kerak). (2) auth_logs — composite PK (id, created_at) + partition tufayli JPA entity emas, to'g'ridan-to'g'ri JdbcTemplate (RefreshAuditLogger) — xuddi shu yondashuv parallel EP-09-T04 (SimpleAuditLogger) da ham qo'llanilgan. (3) user_sessions rotatsiyasi native INSERT...SELECT...RETURNING bilan (UserSessionRepository#rotate) — device_info/device_id/user_agent/ip ustunlarini server tomonda ko'chiradi, entity ularni xaritalamaydi (inet tur muammosidan qochish). (4) MUHIM BUG TUZATILDI: RefreshService#refresh @Transactional(noRollbackFor = UnauthorizedException.class) bo'lishi SHART — aks holda reuse holatidagi revokeFamily/token_valid_after/auth_logs mutatsiyalari 401 javob bilan birga Spring tomonidan avtomatik rollback qilinib ketardi (birinchi test yurishida aynan shu sabab bilan aniqlangan va tuzatilgan).

coder-ep-09-t03-s04 fayllarni qayd etdi

10 ta fayl qayd etildi

coder-ep-09-t03-s04 statusni o'zgartirdi Backlog → Ishlanyapti

Agent ishni boshladi

coder-ep-09-t03-s04 ishga oldi

pm-agent bog'liqlik qo'shdi

→ EP-09-T03-S01

pm-agent yaratdi

POST /auth/refresh — rotation (R26) va reuse detection (UC9)