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
TLDR: "Passwords did not match" is solved by entering the password again when prompted "Confirm" rather than pressing "Enter" to confirm.
When running the saml2aws configure command to login with Okta, the user is prompted Confirm after entering the password. This seems like a very unintuitive way to ask the user to input the same password again. It leads user to press "Enter" to confirm their inputs.
The error message "Passwords did not match" also doesn't make it explicit that the entered password and the confirmed one don't match (obviously because there isn't any confirmed password) and leaves the user perplexed, trying to understand which 2 passwords don't match.
This can be very simply solved by changing the "Confirm" wording to something like "Confirm entered password" or "Enter password again", which is exactly what the CLI is trying to make the user do. An alternative would be to change the error message to "Confirmed password doesn't match".
I tried to open a pull request but I don't have the right permissions to do it. I hope this can be considered as a small but considerable improvement. Cheers!
The text was updated successfully, but these errors were encountered:
ary-b
changed the title
Improve "Configure CLI" prompting
Improve "aws2saml configure" CLI prompting
Feb 4, 2025
ary-b
changed the title
Improve "aws2saml configure" CLI prompting
Improve "saml2aws configure" CLI prompting
Feb 4, 2025
TLDR: "Passwords did not match" is solved by entering the password again when prompted "Confirm" rather than pressing "Enter" to confirm.
When running the
saml2aws configure
command to login with Okta, the user is promptedConfirm
after entering the password. This seems like a very unintuitive way to ask the user to input the same password again. It leads user to press "Enter" to confirm their inputs.The error message "Passwords did not match" also doesn't make it explicit that the entered password and the confirmed one don't match (obviously because there isn't any confirmed password) and leaves the user perplexed, trying to understand which 2 passwords don't match.
This can be very simply solved by changing the "Confirm" wording to something like "Confirm entered password" or "Enter password again", which is exactly what the CLI is trying to make the user do. An alternative would be to change the error message to "Confirmed password doesn't match".
I tried to open a pull request but I don't have the right permissions to do it. I hope this can be considered as a small but considerable improvement. Cheers!
The text was updated successfully, but these errors were encountered: