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
Different ways to get AWS credentials into the Cognito client
publicAmazonCognitoIdentityProviderClientCreateFromKeys(){varcreds=newBasicAWSCredentials("ACCESS_KEY","SECRET_KEY");returnnewAmazonCognitoIdentityProviderClient(creds,RegionEndpoint.USEast1);}publicAmazonCognitoIdentityProviderClientCreateFromProfile(){varcreds=newSharedCredentialsFile();CredentialProfilecognitoProfile;if(!creds.TryGetProfile("cognito",outcognitoProfile)){thrownewException($"Missing credentials for profile: cognito");}varkeys=newBasicAWSCredentials(cognitoProfile.Options.AccessKey,cognitoProfile.Options.SecretKey);returnnewAmazonCognitoIdentityProviderClient(keys,cognitoProfile.Region);}
Thoughts on the API
SignUp should be a user triggered action, and the result is a verified user after they confirm their email (if that is how the user pool is configured). AdminCreateUser should be an admin triggered action, and adds the step of requiring the invited user to change the password to confirm their account.
Not sure why InitiateAuth is not supported for the ADMIN_NO_SRP_AUTH Auth Flow type but for AdminInitiateAuth it is.