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
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:
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>
Run through the sign up process
provide the token
see the error
Expected Behavior
The expected behavior should be that the provided username from the input should be used in the verification step.
The text was updated successfully, but these errors were encountered:
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.
pacu/pacu/modules/cognito__attack/main.py
Line 380 in 4e5f1de
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:
run cognito__attack --identity_pools us-east-1:<identity_pool_id> --user_pool_clients <client_id>@us-east-<id>
Expected Behavior
The expected behavior should be that the provided username from the input should be used in the verification step.
The text was updated successfully, but these errors were encountered: