-
Notifications
You must be signed in to change notification settings - Fork 144
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
[BUG] 401 error after register a customer using an login different from the email. #1464
Labels
Acknowledged
Team has responded to issue
Comments
luanrafael
pushed a commit
to luanrafael/pwa-kit
that referenced
this issue
Oct 5, 2023
10 tasks
luanrafael
pushed a commit
to luanrafael/pwa-kit
that referenced
this issue
Oct 6, 2023
…ration process Issue SalesforceCommerceCloud#1464 Signed-off-by: Luan Rafael Pinheiro <[email protected]>
luanrafael
pushed a commit
to luanrafael/pwa-kit
that referenced
this issue
Oct 6, 2023
…ration process Issue SalesforceCommerceCloud#1464 Signed-off-by: Luan Rafael Pinheiro <[email protected]>
luanrafael
pushed a commit
to luanrafael/pwa-kit
that referenced
this issue
Oct 6, 2023
…ration process Issue SalesforceCommerceCloud#1464 Signed-off-by: Luan Rafael Pinheiro <[email protected]>
wjhsf
pushed a commit
that referenced
this issue
Oct 6, 2023
…ration process (#1465) * Refactor: Use 'login' for authentication instead of 'email' in registration process Issue #1464 Signed-off-by: Luan Rafael Pinheiro <[email protected]> * update changelog Signed-off-by: Luan Rafael Pinheiro <[email protected]> * update changelog Signed-off-by: Luan Rafael Pinheiro <[email protected]> * update changelog Signed-off-by: Luan Rafael Pinheiro <[email protected]> --------- Signed-off-by: Luan Rafael Pinheiro <[email protected]>
Closed via #1465. Thanks for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When attempting to create a new customer account with a custom login (different from the email address), the customer account is successfully created. However, a 401 error is encountered when the registration process tries to authenticate using the email as the username. The issue arises from the assumption within the registration function that the email will always serve as the customer's username, which may not be the case. It is recommended to use the 'login' field instead of the email from the registration body for authentication.
Steps To Reproduce
register.mutateAsync
method with different values for 'login' and 'email':Upon analyzing the requests, a 401 error is observed after the registration request because the function attempts to perform authentication using the email, which, in this case, is not the customer's username.
Expected Result
After the registration request, the user should be authenticated using the provided 'login,' which can be either the email or any other valid information.
Actual Result
After registration, a 401 error occurs because the function attempts to use the email as the username for authentication.
Workaround
Additional Information
It is suggested to replace the usage of the email as the username with the 'login' field in the 'register' function.
The text was updated successfully, but these errors were encountered: