Home Search Pricing Get inErrata About

Sign in Sign up

Graph/session-cookie-not-persisted

Pattern

Session Cookie Not Persisted

session-cookie-not-persisted

A recurring auth failure where login appears to succeed but subsequent requests lose state because session cookies/tokens are not persisted or sent across domains, leading to redirect-to-login loops and 401 responses.

Node Details

Public graph metadata

Updated4/30/2026

Connections

30 linked nodes

Protected routes immediately redirect as if the user is unauthenticated when the app first loads, even though authentication may still be in progress. The `RequiredAuth` component logs `user` as null on initial render and triggers `Navigate` incorrectly.

When the UI calls the `POST /auth/callback/passkey` endpoint. Tension: Origin servers SHOULD NOT fold multiple Set-Cookie header fields into a single header field. Outcome: Cloudflare seem to be in the wrong here.

dashboard login redirects back to login page after successful sign-in

django.security.csrf: Forbidden (Origin checking failed - https://sentry-domain.com does not match any trusted origins.) — /account/recover/ (status_code=403 request=<WSGIRequest: POST '/account/recover/'>). Tension: when it comes to login (correct or wrong username and password). Outcome: It is solved by some steps.

RedirectResponse goes to "/" without the authentication cookie

SessionMiddleware in a FastAPI backend fails to set the session cookie when the React frontend and backend are hosted on different domains/subdomains (e.g., XXX-ui.fly.dev vs XXX-api.fly.dev). The browser rejects the cookie with an 'invalid domain' error and no session is maintained.

were not accessible in js and in browser — Cookies are being set and sent with the next request. Outcome: The problem solved by adding `domain="blueberry.adefe.xyz"` to the cookie in response.

POST https://api.hcaptcha.com/authenticate 401 (Unauthorized) — this is only happening on the web not on the native apps. Tension: {"pass":false,"error-codes":["pat-missing-auth"]}. Outcome: the hcaptcha 401 issue disappeared.

stripe login returns unexpected http status code: 403

Checkout redirect can be faked by appending the success query string or spoofing the HTTP referer

MissingKeyMissing Key-Pair-Id query parameter or cookie value — {urn}/manifest/{derivativeurn}/signedcookies. Tension: I get the following error that suggest I'm missing a header.

Failed to fetch /api/auth/csrf — while integrating it with Keycloak and a custom base path. Tension: Verified the csrf endpoint manually, but it appears to be unreachable. Outcome: I solved it by manually signout.

after logging in, users can access protected routes for 10 seconds. Once the token expires, refreshing the page or navigating should redirect them to the login page. — I’m working on a Next.js project using NextAuth (v5) for authentication. Tension: users can access protected routes for 10 seconds. Outcome: refreshing the page or navigating should redirect them to the login page.

After implementing login with NextAuth, the user session from `getServerSession(authOptions)` does not include a GitHub REST API access token, so API calls requiring a token fail.

`signIn('credentials', ...)` from `next-auth/react` does not authenticate and the app always redirects to the admin page regardless of whether the credentials are correct. The `signIn` response indicates the request succeeds but no proper credential authorization occurs.

After logging out successfully, re-registering or signing in does not reset the Redux state flags `isLogouting` and `isOpeLogoutDialogue` back to `false`, leaving the UI in an incorrect loading/dialog state.

Dispatching the login action logs correctly in the reducer, but the `Auth` function call in `apiInstance.ts` does not execute (or does not run as expected).

the user is not properly logged out by the program, even after I click logout — on the `"Auth Required"` menu (`Auth.razor`). Tension: the expected logout behavior is only applied to the following pages. Outcome: This should resolve the loophole upon logout and user back navigation using the Blazor Identity options.

If at all I login in a new tab and close it. Tension: A Session needs to be maintained for authentication and authorization. Outcome: How can I achieve it?

Embedding a CPQ web app as an iframe inside Salesforce fails to persist authentication cookies/session for API calls. Login in a new tab isn’t recognized inside the Salesforce iframe, preventing authorized requests.

Client-side double-submit CSRF token generation is vulnerable to subdomain hijacking

Confusion about cookie authentication versus token authentication

All routes except /login redirect back to /login

httpOnly cookies are the best way to store tokens safely and protect them from XSS attacks — storing JWTs on the client. Tension: JavaScript won't be allowed to read httpOnly cookies. How would the client handle routes authentication? Outcome: The browser won't automatically set the `Authorization` header like it does with cookies.

jwtAuthFilter was triggered for /api/auth/login even with permitAll() and anyRequest().permitAll()

if(!isSamlRequest) return RedirectToAction(actionName:"login",controllerName: "Account"); — HttpContext.Request.Query.ContainsKey("SAMLRequest") || HttpContext.Request.Headers.ContainsKey("SAMLRequest"). Outcome: return LoginResponse(saml2AuthnRequest.Id, Saml2StatusCodes.Success, requestBinding.RelayState, relyingParty, sessionIndex, claims);.

the browser prevents a potential CSRF attack and doesn't include the token — The call is to the backend endpoint specified earlier in `redirect_uri`. Tension: I need a browser to include the `ASP.NET_SessionId` cookie in the request. Outcome: If I set the `SameSite` cookie attribute to `None` the endpoint can be reached.

I don't think CSRF protection for login forms are useful without also using a phishing attack. — login forms. Tension: They are relevant after a user logs in, in cases where there are forms that act on a user's behalf. Outcome: I wouldn't even generate a session cookie until after a user has logged in.

If I check 'Remember Me' in form, this add a cookie with name "REMEMBERME". Tension: I'm implementing custom authenticator. Outcome: your cookie is normal.

I'm logged out, this happens consistently. — After being logged out I can see in the network tab that a request to google's identitytoolkit, the payload is my idToken, and the response. Tension: is of status code 400 with the TOKEN_EXPIRED error. Outcome: Firebase Auth's persistence is configured.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata