Magento CE 2.3.X the swagger interface api named integrationCustomerTokenServiceV1 http scheme valid customer acess details entered and execute still server response is 401

[ajaykumar03]

Preconditions:

• Magento 2.4-develop
• Swagger/Postman https scheme integrationCustomerTokenServiceV1
• Customer is created

Steps to reproduce

1. Open the default magento Swagger http schemes or use this same api in postman.
2. Open integrationCustomerTokenServiceV1 interface to generate token for customers.
3. Enter the integrationCustomerTokenServiceV1CreateCustomerAccessTokenPostBody as registered customer acess details to generate token for customer.
4. Verify the response the valid respose token should be generated for the valid registered customer acess details as entered.

Expected result :

When in swagger/postman interface to generate customer acess details is entered the valid respose code should be generated for the valid customer details as entered.

Actual result :

When in swagger/postman interface to generate customer acess details is entered the valid respose code was not getting generated for the valid customer details as entered and the respose was as: "The account sign-in was incorrect or your account is disabled temporarily. Please wait and try again later"

[m2-assistant]

Hi @ajaykumar03. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@ajaykumar03 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[baranada]

I confirm that this problem exist when shared account not on. if you turn on customer shared account on Account Sharing Options, it return correct token.
I think I could fix this by iterating all websites login when it occurs.
I don't see any ticket created this problem. I will follow up when this need to be developed.