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
Running the client:auth, code:deploy and code:activate steps using a client ID/Secret combo, and a certificate/Passphrase for 2FA, yet the Authenticator app still fires requiring human interaction when deploying into our Staging environment.
Commands being executed;
node.exe .\node_modules\sfcc-ci\cli.js client:auth $clientID $clientSecret $clientUsername $clientPassword
Hi @irobotbfealy, it appears that through authentication: node.exe .\node_modules\sfcc-ci\cli.js client:auth $clientID $clientSecret $clientUsername $clientPassword
You are authenticating not just with client credentials but also with user credentials. As a consequence, the MFA settings of the user and his primary org are being used through the authentication process and as a result the user is receiving the request to confirm the login in Salesforce authenticator. This blocks automation, of course.
Recommendation is, that you run the authentication only with client credentials but not with user credentials, like: node.exe .\node_modules\sfcc-ci\cli.js client:auth $clientID $clientSecret
Please let us know, if that helps to resolve the issue.
sfcc-ci Version
2.9.1
NodeJS Version
8
sfcc-ci Path
No response
Host OS Details
Bamboo build agent on Windows 10
What happened?
Running the client:auth, code:deploy and code:activate steps using a client ID/Secret combo, and a certificate/Passphrase for 2FA, yet the Authenticator app still fires requiring human interaction when deploying into our Staging environment.
Commands being executed;
node.exe .\node_modules\sfcc-ci\cli.js client:auth $clientID $clientSecret $clientUsername $clientPassword
node.exe .\node_modules\sfcc-ci\cli.js code:deploy --instance $targetsystem $zipfile --certificate $certificatepath --passphrase $passphrase
node.exe .\node_modules\sfcc-ci\cli.js code:activate --instance $targetsystem $codevername
Relevant log output
No response
The text was updated successfully, but these errors were encountered: