Skip to content
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

statusCode: 400, body: { error_description: 'Resource owner authentication failed', error: 'invalid_grant' } } } Error: Authentication failed: Resource owner authentication failed #297

Open
mani762 opened this issue Feb 16, 2022 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@mani762
Copy link

mani762 commented Feb 16, 2022

We are failing to upload our artifacts to all Env , please look this in priority. This is blocking our release activity. Please more logs: statusCode: 400, body: { error_description: 'Resource owner authentication failed', error: 'invalid_grant' } } } Error: Authentication failed: Resource owner authentication failed

@tobiaslohr
Copy link
Contributor

Hi @mani762, users have reported this before in https://sfcc-unofficial.slack.com/archives/CAUFG3SHF. The root cause is that your user account you use to authenticate has a MFA verifier set. Most probably due to your organizations policies in Account Manager of enabling MFA across the org and all roles or widening it to the roles that user has.

In this case the Account Manager revokes the authentication and returns with that error. I recommend, that you switch from the combined client / user authentication to a pure API client authentication using purely the client id and the secret as I assume for the deployments you are anyways seeking for an automation scenario.

@tobiaslohr tobiaslohr added the help wanted Extra attention is needed label Feb 25, 2022
@tobiaslohr
Copy link
Contributor

tobiaslohr commented Mar 7, 2022

In addition we put a document in our wiki at https://github.com/SalesforceCommerceCloud/sfcc-ci/wiki/Resource-Owner-Password-Credentials-Authentication-Failure which describes how to resolve this.

@tobiaslohr
Copy link
Contributor

@mani762 Did the above help you to resolve your issue and can we close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants