Skip to content

TASK: Expose internal auth session-state validation #254

Closed

Description

@ramioooz

Parent: #46
Related: #47
Service: auth-service

Objective

Expose the existing authoritative JWT plus server-side session validation port through a service-local internal HTTP boundary for downstream protected-service consumers.

Scope

  • Add a bearer-protected session validation endpoint that returns the authenticated subject and session ID.
  • Preserve the existing signed JWT, PostgreSQL session state, revocation, and single-session policy behavior.
  • Return the existing stable Problem Details contracts for invalid and revoked tokens.
  • Add only focused integration verification for the new boundary.

Out of scope

  • Terminal/event publication or consumption.
  • API Gateway routing or policy changes.
  • AWS/UAT/PROD provisioning, JWKS, MFA, or refresh-token work.

Acceptance criteria

  • A valid active token returns its subject and session ID.
  • A token revoked by a later REVOKE_PREVIOUS login is rejected.
  • Missing, malformed, and invalid bearer credentials remain unauthorized.
  • Maven verification, Helm validation, and diff checks pass.

Activity

  1. self-assigned this
    on Sep 7, 2026
  2. ramioooz commented on Sep 7, 2026

    @ramioooz
    MemberAuthor

    Completed through merged auth-service #13.

    • Added the bearer-protected internal GET /api/v1/auth/session validation boundary.
    • Preserved the authoritative JWT, PostgreSQL session state, revocation, and single-session policy behavior.
    • Added focused integration coverage for valid, revoked, missing, malformed, and invalid bearer credentials.
    • Maven verification, Helm validation, and container smoke checks all passed in the pull request.
    • Corrected this Project item to Sprint 4, native Task type, Auth & Session Management, auth-service, and parent story .github#46.

    No public gateway route, AWS/UAT/PROD work, or redundant test suite was added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions