Repository navigation
feat: add browser sessions and API authorization - #3
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Static browser applications need same-origin authentication without exposing JWTs to JavaScript. Add CSRF preparation, login-to-HttpOnly-cookie exchange, current-profile lookup and logout endpoints, while retaining explicit Bearer clients. Permit anonymous catalog GETs, require ROLE_ADMIN for product/account administration, and block public internal credential routes.
Cookie authentication requires CSRF for unsafe requests; login also requires CSRF. Cookies default to Secure, HttpOnly and SameSite=Lax with /api scope. Local HTTP Compose explicitly overrides Secure.
Validation: Maven verify passed eight tests and the configured coverage gate, including a real CSRF cookie/header and login/profile exchange against local upstream fixtures. The workstation override was -Djava.version=24; the repository target remains Java 25. No new dependencies.
AI-assisted implementation/docs. Full Product authorization and production configuration require separate acceptance.