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

username overwrite #412

Closed
EduardSchwarzkopf opened this issue Mar 16, 2024 · 1 comment
Closed

username overwrite #412

EduardSchwarzkopf opened this issue Mar 16, 2024 · 1 comment

Comments

@EduardSchwarzkopf
Copy link
Contributor

Describe the Bug
When you don't provide a username in the run command the signup function will then ask the user to provide a username, which is fine. But on the verify call, the username from the input is being used, but the args username, which is since not provided falls back to the default one.

This creates a problem when providing the correct confirmation token to the prompt because this will then create a mismatch between the username and token data.

To Reproduce
Steps to reproduce the behavior:

  1. Run the command without a username flag:
    run cognito__attack --identity_pools us-east-1:<identity_pool_id> --user_pool_clients <client_id>@us-east-<id>
  2. Run through the sign up process
  3. provide the token
  4. see the error

Expected Behavior
The expected behavior should be that the provided username from the input should be used in the verification step.

@DaveYesland
Copy link
Collaborator

Closed in #413

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

2 participants