/

POST

Initiates the authentication flow, as an administrator.

Calling this action requires developer credentials.

Request Example

Shell

JavaScript

Java

Swift

curl --location --request POST '/' \
--header 'X-Amz-Target;' \
--header 'Content-Type: application/json' \
--data-raw '{
    "UserPoolId": "string",
    "ClientId": "string",
    "AuthFlow": "USER_SRP_AUTH",
    "AuthParameters": {
        "property1": "string",
        "property2": "string"
    },
    "ClientMetadata": {
        "property1": "string",
        "property2": "string"
    },
    "AnalyticsMetadata": {},
    "ContextData": {
        "IpAddress": "string",
        "ServerName": "string",
        "ServerPath": "string",
        "HttpHeaders": [],
        "EncodedData": "string"
    }
}'

Response Example

200 - Example 1

{
    "ChallengeName": "SMS_MFA",
    "Session": "string",
    "ChallengeParameters": {
        "property1": "string",
        "property2": "string"
    },
    "AuthenticationResult": {
        "AccessToken": "string",
        "ExpiresIn": 0,
        "TokenType": "string",
        "RefreshToken": "string",
        "IdToken": "string",
        "NewDeviceMetadata": {
            "DeviceKey": "string",
            "DeviceGroupKey": "string"
        }
    }
}

Request

Header Params

X-Amz-Target

string

required

Body Params application/json

Initiates the authorization request, as an administrator.

UserPoolId

string

required

The ID of the Amazon Cognito user pool.

>= 1 characters<= 55 characters

Match pattern:

[\w-]+_[0-9a-zA-Z]+

ClientId

string <password>

required

The app client ID.

>= 1 characters<= 128 characters

Match pattern:

[\w+]+

AuthFlow

enum<string>

required

The authentication flow for this call to run. The API action will depend on this value. For example:

REFRESH_TOKEN_AUTH will take in a valid refresh token and return new tokens.
USER_SRP_AUTH will take in USERNAME and SRP_A and return the Secure Remote Password (SRP) protocol variables to be used for next challenge execution.
ADMIN_USER_PASSWORD_AUTH will take in USERNAME and PASSWORD and return the next challenge or tokens.

Valid values include:

USER_SRP_AUTH: Authentication flow for the Secure Remote Password (SRP) protocol.
REFRESH_TOKEN_AUTH/REFRESH_TOKEN: Authentication flow for refreshing the access token and ID token by supplying a valid refresh token.
CUSTOM_AUTH: Custom authentication flow.
ADMIN_NO_SRP_AUTH: Non-SRP authentication flow; you can pass in the USERNAME and PASSWORD directly if the flow is enabled for calling the app client.
ADMIN_USER_PASSWORD_AUTH: Admin-based user password authentication. This replaces the ADMIN_NO_SRP_AUTH authentication flow. In this flow, Amazon Cognito receives the password in the request instead of using the SRP process to verify passwords.

Allowed values:

USER_SRP_AUTHREFRESH_TOKEN_AUTHREFRESH_TOKENCUSTOM_AUTHADMIN_NO_SRP_AUTHUSER_PASSWORD_AUTHADMIN_USER_PASSWORD_AUTH

AuthParameters

object

optional

The authentication parameters. These are inputs corresponding to the AuthFlow that you're invoking. The required values depend on the value of AuthFlow:

For USER_SRP_AUTH: USERNAME (required), SRP_A (required), SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY.
For REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY.
For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app client is configured with client secret), PASSWORD (required), DEVICE_KEY.
For CUSTOM_AUTH: USERNAME (required), SECRET_HASH (if app client is configured with client secret), DEVICE_KEY. To start the authentication flow with password verification, include ChallengeName: SRP_A and SRP_A: (The SRP_A Value).

ClientMetadata

object

optional

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 Lambda functions to user pool triggers. When you use the AdminInitiateAuth API action, Amazon Cognito invokes the Lambda functions that are specified for various triggers. The ClientMetadata value is passed as input to the functions for only the following triggers:

Pre signup
Pre authentication
User migration

When Amazon Cognito invokes the functions for these triggers, it passes a JSON payload, which the function receives as input. This payload contains a validationData attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminInitiateAuth request. In your function code in Lambda, you can process the validationData value to enhance your workflow for your specific needs.

When you use the AdminInitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it doesn't provide the ClientMetadata value as input:

Post authentication
Custom message
Pre token generation
Create auth challenge
Define auth challenge
Verify auth challenge

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

AnalyticsMetadata

object

optional

The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls.

ContextData

object

optional

Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests.

IpAddress

string

required

The source IP address of your user's device.

ServerName

string

required

Your server endpoint where this API is invoked.

ServerPath

string

required

Your server path where this API is invoked.

HttpHeaders

array[object (HttpHeader) {2}]

required

HttpHeaders received on your server in same order.

EncodedData

string

optional

Encoded device-fingerprint details that your app collected with the Amazon Cognito context data collection library. For more information, see Adding user device and session data to API requests.

Examples

Responses

🟢200Success

application/json

Body

Initiates the authentication response, as an administrator.

ChallengeName

enum<string>

optional

The name of the challenge that you're responding to with this call. This is returned in the AdminInitiateAuth response if you must pass another challenge.

MFA_SETUP: If MFA is required, users who don't have at least one of the MFA methods set up are presented with an MFA_SETUP challenge. The user must set up at least one MFA type to continue to authenticate.
SELECT_MFA_TYPE: Selects the MFA type. Valid MFA options are SMS_MFA for text SMS MFA, and SOFTWARE_TOKEN_MFA for time-based one-time password (TOTP) software token MFA.
SMS_MFA: Next challenge is to supply an SMS_MFA_CODE, delivered via SMS.
PASSWORD_VERIFIER: Next challenge is to supply PASSWORD_CLAIM_SIGNATURE, PASSWORD_CLAIM_SECRET_BLOCK, and TIMESTAMP after the client-side SRP calculations.
CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued.
DEVICE_SRP_AUTH: If device tracking was activated in your user pool and the previous challenges were passed, this challenge is returned so that Amazon Cognito can start tracking this device.
DEVICE_PASSWORD_VERIFIER: Similar to PASSWORD_VERIFIER, but for devices only.
ADMIN_NO_SRP_AUTH: This is returned if you must authenticate with USERNAME and PASSWORD directly. An app client must be enabled to use this flow.
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login. Respond to this challenge with NEW_PASSWORD and any required attributes that Amazon Cognito returned in the requiredAttributes parameter. You can also set values for attributes that aren't required by your user pool and that your app client can write. For more information, see AdminRespondToAuthChallenge.
MFA_SETUP: For users who are required to set up an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parameters MFA_CAN_SETUP value.

To set up software token MFA, use the session returned here from InitiateAuth as an input to AssociateSoftwareToken, and use the session returned by VerifySoftwareToken as an input to RespondToAuthChallenge with challenge name MFA_SETUP to complete sign-in. To set up SMS MFA, users will need help from an administrator to add a phone number to their account and then call InitiateAuth again to restart sign-in.

Allowed values:

SMS_MFASOFTWARE_TOKEN_MFASELECT_MFA_TYPEMFA_SETUPPASSWORD_VERIFIERCUSTOM_CHALLENGEDEVICE_SRP_AUTHDEVICE_PASSWORD_VERIFIERADMIN_NO_SRP_AUTHNEW_PASSWORD_REQUIRED

Session

string

optional

The session that should be passed both ways in challenge-response calls to the service. If AdminInitiateAuth or AdminRespondToAuthChallenge API call determines that the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next AdminRespondToAuthChallenge API call.

>= 20 characters<= 2048 characters

ChallengeParameters

object

optional

The challenge parameters. These are returned to you in the AdminInitiateAuth response if you must pass another challenge. The responses in this parameter should be used to compute inputs to the next call (AdminRespondToAuthChallenge).

All challenges require USERNAME and SECRET_HASH (if applicable).

The value of the USER_ID_FOR_SRP attribute is the user's actual username, not an alias (such as email address or phone number), even if you specified an alias in your call to AdminInitiateAuth. This happens because, in the AdminRespondToAuthChallenge API ChallengeResponses, the USERNAME attribute can't be an alias.

AuthenticationResult

object

optional

The result of the authentication response. This is only returned if the caller doesn't need to pass another challenge. If the caller does need to pass another challenge before it gets tokens, ChallengeName, ChallengeParameters, and Session are returned.

AccessToken

string <password>

optional

A valid access token that Amazon Cognito issued to the user who you want to authenticate.

Match pattern:

[A-Za-z0-9-_=.]+

ExpiresIn

integer

optional

The expiration period of the authentication result in seconds.

TokenType

string

optional

The token type.

RefreshToken

string <password>

optional

The refresh token.

Match pattern:

[A-Za-z0-9-_=.]+

IdToken

string <password>

optional

The ID token.

Match pattern:

[A-Za-z0-9-_=.]+

NewDeviceMetadata

object

optional

The new device metadata from an authentication result.

🟠480ResourceNotFoundException

🟠481InvalidParameterException

🟠482NotAuthorizedException

🟠483TooManyRequestsException

🟠484InternalErrorException

🟠485UnexpectedLambdaException

🟠486InvalidUserPoolConfigurationException

🟠487UserLambdaValidationException

🟠488InvalidLambdaResponseException

🟠489MFAMethodNotFoundException

🟠490InvalidSmsRoleAccessPolicyException

🟠491InvalidSmsRoleTrustRelationshipException

🟠492PasswordResetRequiredException

🟠493UserNotFoundException

🟠494UserNotConfirmedException

Modified at 2023-08-15 07:11:06