B2B User Can't Login to Storefront, "errorCode":"60011"
(Doc ID 2345813.1)
Last updated on JUNE 20, 2024
Applies to:
Oracle Commerce Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
A new B2B user account has been created, but when trying to log in to the storefront that user is unable to log in.
On the Storefront the following error is displayed "There is a problem with your account. Please contact your account administrator."
If logging in through API we see, {"errorCode":"60011","message":"Unauthorized Access","status":"401"}
Note that these errors messages are different than the error messages that are seen when using a incorrect set of credentials.
The default "Log-on unsuccessful. The details you entered do not match our records, please try again." messaging is seen on the storefront for accounts with bad credentials.
Endpoint response for bad credentials is still a 401, but there would not be a 60011 error code.
The default "Log-on unsuccessful. The details you entered do not match our records, please try again." messaging is seen on the storefront for accounts with bad credentials.
Endpoint response for bad credentials is still a 401, but there would not be a 60011 error code.
Changes
A new B2B user account has been created.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |