PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` package Paws::CognitoIdp::InitiateAuth; use Moose; has AnalyticsMetadata => (is => 'ro', isa => 'Paws::CognitoIdp::AnalyticsMetadataType'); has AuthFlow => (is => 'ro', isa => 'Str', required => 1); has AuthParameters => (is => 'ro', isa => 'Paws::CognitoIdp::AuthParametersType'); has ClientId => (is => 'ro', isa => 'Str', required => 1); has ClientMetadata => (is => 'ro', isa => 'Paws::CognitoIdp::ClientMetadataType'); has UserContextData => (is => 'ro', isa => 'Paws::CognitoIdp::UserContextDataType'); use MooseX::ClassAttribute; class_has _api_call => (isa => 'Str', is => 'ro', default => 'InitiateAuth'); class_has _returns => (isa => 'Str', is => 'ro', default => 'Paws::CognitoIdp::InitiateAuthResponse'); class_has _result_key => (isa => 'Str', is => 'ro'); 1; ### main pod documentation begin ### =head1 NAME Paws::CognitoIdp::InitiateAuth - Arguments for method InitiateAuth on L =head1 DESCRIPTION This class represents the parameters used for calling the method InitiateAuth on the L service. Use the attributes of this class as arguments to method InitiateAuth. You shouldn't make instances of this class. Each attribute should be used as a named argument in the call to InitiateAuth. =head1 SYNOPSIS my $cognito-idp = Paws->service('CognitoIdp'); my $InitiateAuthResponse = $cognito -idp->InitiateAuth( AuthFlow => 'USER_SRP_AUTH', ClientId => 'MyClientIdType', AnalyticsMetadata => { AnalyticsEndpointId => 'MyStringType', # OPTIONAL }, # OPTIONAL AuthParameters => { 'MyStringType' => 'MyStringType', # key: OPTIONAL, value: OPTIONAL }, # OPTIONAL ClientMetadata => { 'MyStringType' => 'MyStringType', # key: OPTIONAL, value: OPTIONAL }, # OPTIONAL UserContextData => { EncodedData => 'MyStringType', # OPTIONAL }, # OPTIONAL ); # Results: my $AuthenticationResult = $InitiateAuthResponse->AuthenticationResult; my $ChallengeName = $InitiateAuthResponse->ChallengeName; my $ChallengeParameters = $InitiateAuthResponse->ChallengeParameters; my $Session = $InitiateAuthResponse->Session; # Returns a L object. Values for attributes that are native types (Int, String, Float, etc) can passed as-is (scalar values). Values for complex Types (objects) can be passed as a HashRef. The keys and values of the hashref will be used to instance the underlying object. For the AWS API documentation, see L =head1 ATTRIBUTES =head2 AnalyticsMetadata => L The Amazon Pinpoint analytics metadata for collecting metrics for C calls. =head2 B AuthFlow => Str The authentication flow for this call to execute. The API action will depend on this value. For example: =over =item * C will take in a valid refresh token and return new tokens. =item * C will take in C and C and return the SRP variables to be used for next challenge execution. =item * C will take in C and C and return the next challenge or tokens. =back Valid values include: =over =item * C: Authentication flow for the Secure Remote Password (SRP) protocol. =item * C/C: Authentication flow for refreshing the access token and ID token by supplying a valid refresh token. =item * C: Custom authentication flow. =item * C: Non-SRP authentication flow; USERNAME and PASSWORD are passed directly. If a user migration Lambda trigger is set, this flow will invoke the user migration Lambda if the USERNAME is not found in the user pool. =item * C: Admin-based user password authentication. This replaces the C authentication flow. In this flow, Cognito receives the password in the request instead of using the SRP process to verify passwords. =back C is not a valid value. Valid values are: C<"USER_SRP_AUTH">, C<"REFRESH_TOKEN_AUTH">, C<"REFRESH_TOKEN">, C<"CUSTOM_AUTH">, C<"ADMIN_NO_SRP_AUTH">, C<"USER_PASSWORD_AUTH">, C<"ADMIN_USER_PASSWORD_AUTH"> =head2 AuthParameters => L The authentication parameters. These are inputs corresponding to the C that you are invoking. The required values depend on the value of C: =over =item * For C: C (required), C (required), C (required if the app client is configured with a client secret), C. =item * For C: C (required), C (required if the app client is configured with a client secret), C. =item * For C: C (required), C (if app client is configured with client secret), C. To start the authentication flow with password verification, include C and C. =back =head2 B ClientId => Str The app client ID. =head2 ClientMetadata => L A map of custom key-value pairs that you can provide as input for certain custom workflows that this action triggers. You create custom workflows by assigning AWS Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the AWS Lambda functions that are specified for various triggers. The ClientMetadata value is passed as input to the functions for only the following triggers: =over =item * Pre signup =item * Pre authentication =item * User migration =back When Amazon Cognito invokes the functions for these triggers, it passes a JSON payload, which the function receives as input. This payload contains a C attribute, which provides the data that you assigned to the ClientMetadata parameter in your InitiateAuth request. In your function code in AWS Lambda, you can process the C value to enhance your workflow for your specific needs. When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it does not provide the ClientMetadata value as input: =over =item * Post authentication =item * Custom message =item * Pre token generation =item * Create auth challenge =item * Define auth challenge =item * Verify auth challenge =back For more information, see Customizing User Pool Workflows with Lambda Triggers (https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html) in the I. Take the following limitations into consideration when you use the ClientMetadata parameter: =over =item * Amazon Cognito does not store the ClientMetadata value. This data is available only to AWS Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration does not include triggers, the ClientMetadata parameter serves no purpose. =item * Amazon Cognito does not validate the ClientMetadata value. =item * Amazon Cognito does not encrypt the the ClientMetadata value, so don't use it to provide sensitive information. =back =head2 UserContextData => L Contextual data such as the user's device fingerprint, IP address, or location used for evaluating the risk of an unexpected event by Amazon Cognito advanced security. =head1 SEE ALSO This class forms part of L, documenting arguments for method InitiateAuth in L =head1 BUGS and CONTRIBUTIONS The source code is located here: L Please report bugs to: L =cut