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

Authentication failes with a 45 character password #141

Closed
kschaefers-engelhorn opened this issue Apr 14, 2020 · 1 comment
Closed

Authentication failes with a 45 character password #141

kschaefers-engelhorn opened this issue Apr 14, 2020 · 1 comment

Comments

@kschaefers-engelhorn
Copy link

Problem: When running sfcc-ci client:auth I received a 504 Gateway timeout with a password that had 45 characters. There were no special characters in the password - only letters and numbers. After a long seach and comparisons to colleagues where the command with the same version of sfcc-ci worked without any problems I changed my password to 32 characters and even included special characters. Since changing the password the command works like a charm!

As the only thing I've changed is the length of the password it seems to me that there is a problem in case the password is too long and the timeout error message is not helping when trying to figure out the problem. I was able to log into the account manager and instances with this password without any problems.

Another thing that makes me sure that this is a problem within sfcc-ci: I've tried the command on 3 different setups. All had the same result with the timeout and worked like a charm when using a dw.json of a colleague with a shorter password.

Please either notify the user in case the password is longer than sfcc-ci can handle with a corresponding error message or even better: make it possible to have long passwords when using sfcc-ci.

@kschaefers-engelhorn
Copy link
Author

After looking at this again and tying one more time it seems to me that the Authenticator App might have not have responded to the 2 factor authentication or so - I currently can not reproduce this and therefore I'll close the ticket and let you know in case I have a better description of how to reproduce the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant