-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why send JWTs two different ways? #53
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current explainer says that when a session is being established, the JWT which contains the signed challenge is sent as the POST body data to the
/path+"/startsession"
endpoint. When the session is being refreshed however, despite there being a separate URL/path+"/refresh"
used, the JWT signing the challenge is depicted as being sent in a headerSec-Session-Response
.It seems odd to have two different approaches for sending the JWT. Why not use either POST body, or a header, in both use cases?
The text was updated successfully, but these errors were encountered: