You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2021. It is now read-only.
When using TSec / Http4s, it looks like parsing the JWT subject is buggy when the type is String. The requests then all fail with an Unauthorized error.
TL;DR; the jwt subject should contain an opening double quote (and probably a closing one) to be parsed as a string (the id type I have chosen) by the json parser (jawn), as far as I understand. A decent workaround would be to use an Int, but I prefer using a String.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using TSec / Http4s, it looks like parsing the JWT subject is buggy when the type is
String
. The requests then all fail with an Unauthorized error.I can reproduce this behaviour with a sample application here: https://github.com/cdelmas/tsec-http4s-case-1 (instructions to reproduce in the README).
TL;DR; the jwt subject should contain an opening double quote (and probably a closing one) to be parsed as a string (the id type I have chosen) by the json parser (jawn), as far as I understand. A decent workaround would be to use an
Int
, but I prefer using aString
.The text was updated successfully, but these errors were encountered: