package Paws::CognitoIdp::InitiateAuthResponse; use Moose; has AuthenticationResult => (is => 'ro', isa => 'Paws::CognitoIdp::AuthenticationResultType'); has ChallengeName => (is => 'ro', isa => 'Str'); has ChallengeParameters => (is => 'ro', isa => 'Paws::CognitoIdp::ChallengeParametersType'); has Session => (is => 'ro', isa => 'Str'); has _request_id => (is => 'ro', isa => 'Str'); ### main pod documentation begin ### =head1 NAME Paws::CognitoIdp::InitiateAuthResponse =head1 ATTRIBUTES =head2 AuthenticationResult => L The result of the authentication response. This is only returned if the caller does not need to pass another challenge. If the caller does need to pass another challenge before it gets tokens, C, C, and C are returned. =head2 ChallengeName => Str The name of the challenge which you are responding to with this call. This is returned to you in the C response if you need to pass another challenge. Valid values include the following. Note that all of these challenges require C and C (if applicable) in the parameters. =over =item * C: Next challenge is to supply an C, delivered via SMS. =item * C: Next challenge is to supply C, C, and C after the client-side SRP calculations. =item * C: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued. =item * C: If device tracking was enabled on your user pool and the previous challenges were passed, this challenge is returned so that Amazon Cognito can start tracking this device. =item * C: Similar to C, but for devices only. =item * C: For users who are required to change their passwords after successful first login. This challenge should be passed with C and any other required attributes. =item * C: For users who are required to setup an MFA factor before they can sign-in. The MFA types enabled for the user pool will be listed in the challenge parameters C value. To setup software token MFA, use the session returned here from C as an input to C, and use the session returned by C as an input to C with challenge name C to complete sign-in. To setup SMS MFA, users will need help from an administrator to add a phone number to their account and then call C again to restart sign-in. =back Valid values are: C<"SMS_MFA">, C<"SOFTWARE_TOKEN_MFA">, C<"SELECT_MFA_TYPE">, C<"MFA_SETUP">, C<"PASSWORD_VERIFIER">, C<"CUSTOM_CHALLENGE">, C<"DEVICE_SRP_AUTH">, C<"DEVICE_PASSWORD_VERIFIER">, C<"ADMIN_NO_SRP_AUTH">, C<"NEW_PASSWORD_REQUIRED"> =head2 ChallengeParameters => L The challenge parameters. These are returned to you in the C response if you need to pass another challenge. The responses in this parameter should be used to compute inputs to the next call (C). All challenges require C and C (if applicable). =head2 Session => Str The session which should be passed both ways in challenge-response calls to the service. If the caller needs to go through another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next C API call. =head2 _request_id => Str =cut 1;