Header error regarding JWT implementation
See original GitHub issueFirst off, Thank you so much for your project (time and effort!). On this moment I’m experiencing some errors regarding the JWT header (name/value) combination.
The error throw = Illegal request header: Illegal 'authorization' header: Invalid input '=', expected auth-param, OWS, token68, 'EOI' or tchar
Using the directive optionalSession(oneOff, usingHeaders)
This directive always returns an Option[T] containing a None
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Issues with CORS headers JWT error for API Gateway
We're having some issues with using our Cloud Run application with API Gateway serving calls. Since we implement JWT token timeout we would...
Read more >Troubleshooting JWT validation - Google Cloud
Error: BAD_FORMAT Check the following: Make sure the JWT contains valid JSON. Check that the JWT header has the "alg" field and is...
Read more >Decode JWT runtime error troubleshooting | Apigee Edge
This error occurs if the JSON Web Token (JWT) specified in the <Source> element of the Decode JWT policy is malformed, invalid or...
Read more >Using JWT? You need avoid these implementation mistakes
Leak the JWT in referrer header. It is common that a developer attaches the JWT in a URL, for example, user registering and...
Read more >JSON Web Token Introduction - jwt.io
The header typically consists of two parts: the type of the token, which is JWT, and the signing algorithm being used, such as...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have the same issue.
I have similar problem… any suggestions … by the way , I am not using akka-http-session lib at the client side. It is not produced at the local but at the server after deployment