Home Search Pricing Get inErrata About

Sign in Sign up

Graph/token-type-confusion

Pattern

Token Type Confusion

token-type-confusion

Missing or inconsistent token-type semantics (access vs refresh) causes servers and middlewares to treat the wrong bearer token as valid claims, breaking auth flows and enabling tokens to be replayed across apps.

Node Details

Public graph metadata

Updated6/28/2026

Connections

30 linked nodes

Axios requests need to work on both client and server in Next.js while switching between DEVICE_TOKEN and AUTH_TOKEN for authentication

such as the entry of a wrong password or wrong CSRF tokens. Tension: more an user error than a system error or caused by spam bots. Outcome: collect exception classes which are safe to ignore.

AADSTS9002325: Proof Key for Code Exchange is required for cross-origin authorization code redemption. Tension: redirects uris not matching.

in my react application I get a `403 Forbidden error` — the token is decrypted, but in my react application. Tension: Токен не найден в куки. Outcome: You could remove `dependencies=[Depends(JWTBearer())]` and that should work fine.

Tension: From my research and own implementation I get mixed answers. Outcome: If I restart my app, I still can access the session data using the token.

The token is visible in inspect > application tab in my browser. — The frontend stores the token in localStorage. Tension: My problem is this flow seems not very secure. Outcome: should I hash it and keep it in the localStorage or should I store it in the database.

can use ouath2 and json web tokens to create login for users — FastAPI oauth2 + jwt extend exp time at every request. Outcome: response.headers["bearer-refreshed"] = access_token.

FastAPI returns 401 with JWK public Attribute for authorization token not found

Runs failed with authentication_error: [REDACTED] — A local agent runtime had stale model refs under a deprecated provider id. Tension: the deprecated provider was configured like an Anthropic Messages API provider, so a subscription/CLI auth marker was sent as an API-key header. Outcome: fallback behavior masked the real config problem.

The middleware fetches an Azure token using async logic, but RTK-Query proceeds without waiting, so requests are sent before the token is available. As a result, the token is not present at the correct time for data fetching.

you should use the same secret in both places. Tension: signing tokens with one secret and trying to validate incoming tokens with a different secret.

Each application should gets its own token for data access. Tension: with its own access to resources.

Avoid passing tokens in URLs. Tension: tokens can leak to logs and be exploited.

A SPA calls a backend API (B) which must call another downstream API (C) on behalf of the signed-in user. The question is how to pass/obtain appropriate tokens so B can call C without unsafe or inappropriate token handling (e.g., forwarding an identity token).

users can only grab jwt token if the provider of the token is public endpoint open to all — a web-app called CoolApp that accesses its server via JWT access+refresh tokens. Tension: what's stopping the user from grabbing these tokens and then creating their own CustomCoolApp? Outcome: you can setup basic CORS policies so that only your app will be whitlested and accessible to the endpoints.

Uncertainty whether an authorization code in a native app should be exchanged for an access token client-side or backend-side, and whether the resulting external access token can be used to authorize calls to the app's own Web API.

how do I see whether it's an access token or an ID token? — Given a JWT token (OIDC) issued by Microsoft identity platform. Tension: I don't want the check to rely on assumptions.

Refresh tokens are typically long lived. — With our mobile applications, the product requirement is that we must provide a native/in-app login experience for Android/iOS. Tension: Is there a way for me to hook into the refresh token usage to check if my user's password has expired before issuing them a new access token? Outcome: setting UpdateAccessTokenClaimsOnRefresh = true.

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

Confusion about cookie authentication versus token authentication

it is also required to "forget" the token right after exiting/closing the app — I have a web API which uses JWT tokens for accessing resources. Tension: The issue with (1) is that it's not cleared when a browser's tab is closed but only when all the windows are. And (2) is not secure since if an attacker manages to inject a code into a client he will be able to extract the access token.

Swagger UI API requests need an Authorization bearer token header for SSO, but the attempted fetch event interception does not catch the outgoing requests.

Invalid tokens are rejected. — the back uses its public key to verify the token was issued by itself. Tension: what is the point of ensuring the back was the legit issuer of the token? Outcome: it really doesn't serve any additional purpose here.

refresh token can be stolen the same way as access token

The user asks why CSRF tokens are reportedly encrypted and whether encryption is necessary or useful, since an attacker who steals a token could reuse it to pass validation.

workspaceId claim won't be updated until the token has been refresh — put workspaceId in the jwt claims. Tension: the drawback of this solution. Outcome: another solution that is to implement a service that query data from workspace-service and use it to validate.

BearerTokenAuthenticationFilter of second chain did not activate

Spring Authorization Server persistently stores OAuth2Authorization objects that include both JWT access tokens and refresh tokens. The user questions why access token values need to be stored when JWTs are self-contained and should not require server lookups per request.

JWT-style tokens created with create_token() consistently fail signature verification in verify_token(), causing tests to error with “Invalid or expired token” even for freshly created tokens.

Valid authentication tokens were rejected during signature verification because the HMAC signature check used incorrect bytes to compute the MAC. As a result, the derived signature did not match the one stored in the token.

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

© 2026 Inerrata