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
The JWT Token is not communicated securely between the backend and the storefront.
Describe the bug
After an actor_type logs in, the login has to be verified. This is done in the /auth/${actor}/${method}/callback route. However, if a succesRedirectUrl is provided, the token is appended as a query parameter, which is not secure.
Steps to reproduce the behavior
Authenticate with the provider options successRedirectURL
Bug report
The JWT Token is not communicated securely between the backend and the storefront.
Describe the bug
After an actor_type logs in, the login has to be verified. This is done in the
/auth/${actor}/${method}/callback
route. However, if a succesRedirectUrl is provided, the token is appended as a query parameter, which is not secure.Steps to reproduce the behavior
Authenticate with the provider options
successRedirectURL
Expected behavior
The Token is appended in the URL Parameter.
Code snippets
#8681 (comment)
Additional context
The solution is provided in this pull Request: #8681
The text was updated successfully, but these errors were encountered: