@Generated(value="software.amazon.awssdk:codegen") public final class InitiateAuthResponse extends CognitoIdentityProviderResponse implements ToCopyableBuilder<InitiateAuthResponse.Builder,InitiateAuthResponse>
Initiates the authentication response.
| Modifier and Type | Class and Description |
|---|---|
static interface |
InitiateAuthResponse.Builder |
| Modifier and Type | Method and Description |
|---|---|
AuthenticationResultType |
authenticationResult()
The result of the authentication response.
|
static InitiateAuthResponse.Builder |
builder() |
ChallengeNameType |
challengeName()
The name of the challenge which you are responding to with this call.
|
String |
challengeNameAsString()
The name of the challenge which you are responding to with this call.
|
Map<String,String> |
challengeParameters()
The challenge parameters.
|
boolean |
equals(Object obj) |
boolean |
equalsBySdkFields(Object obj) |
<T> Optional<T> |
getValueForField(String fieldName,
Class<T> clazz) |
boolean |
hasChallengeParameters()
Returns true if the ChallengeParameters property was specified by the sender (it may be empty), or false if the
sender did not specify the value (it will be empty).
|
int |
hashCode() |
List<SdkField<?>> |
sdkFields() |
static Class<? extends InitiateAuthResponse.Builder> |
serializableBuilderClass() |
String |
session()
The session which should be passed both ways in challenge-response calls to the service.
|
InitiateAuthResponse.Builder |
toBuilder() |
String |
toString()
Returns a string representation of this object.
|
responseMetadatasdkHttpResponseclone, finalize, getClass, notify, notifyAll, wait, wait, waitcopypublic final ChallengeNameType challengeName()
The name of the challenge which you are responding to with this call. This is returned to you in the
AdminInitiateAuth response if you need to pass another challenge.
Valid values include the following. Note that all of these challenges require USERNAME and
SECRET_HASH (if applicable) in the parameters.
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 enabled on 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.
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first
login. This challenge should be passed with NEW_PASSWORD and any other required attributes.
MFA_SETUP: 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 MFA_CAN_SETUP value.
To setup 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 setup
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.
If the service returns an enum value that is not available in the current SDK version, challengeName
will return ChallengeNameType.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available
from challengeNameAsString().
AdminInitiateAuth response if you need to pass another challenge.
Valid values include the following. Note that all of these challenges require USERNAME and
SECRET_HASH (if applicable) in the parameters.
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 enabled on 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.
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful
first login. This challenge should be passed with NEW_PASSWORD and any other required
attributes.
MFA_SETUP: 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 MFA_CAN_SETUP
value.
To setup 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 setup 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.
ChallengeNameTypepublic final String challengeNameAsString()
The name of the challenge which you are responding to with this call. This is returned to you in the
AdminInitiateAuth response if you need to pass another challenge.
Valid values include the following. Note that all of these challenges require USERNAME and
SECRET_HASH (if applicable) in the parameters.
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 enabled on 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.
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first
login. This challenge should be passed with NEW_PASSWORD and any other required attributes.
MFA_SETUP: 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 MFA_CAN_SETUP value.
To setup 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 setup
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.
If the service returns an enum value that is not available in the current SDK version, challengeName
will return ChallengeNameType.UNKNOWN_TO_SDK_VERSION. The raw value returned by the service is available
from challengeNameAsString().
AdminInitiateAuth response if you need to pass another challenge.
Valid values include the following. Note that all of these challenges require USERNAME and
SECRET_HASH (if applicable) in the parameters.
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 enabled on 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.
NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful
first login. This challenge should be passed with NEW_PASSWORD and any other required
attributes.
MFA_SETUP: 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 MFA_CAN_SETUP
value.
To setup 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 setup 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.
ChallengeNameTypepublic final String session()
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 RespondToAuthChallenge API call.
RespondToAuthChallenge API call.public final boolean hasChallengeParameters()
public final Map<String,String> challengeParameters()
The challenge parameters. These are returned to you in the InitiateAuth response if you need to pass
another challenge. The responses in this parameter should be used to compute inputs to the next call (
RespondToAuthChallenge).
All challenges require USERNAME and SECRET_HASH (if applicable).
Attempts to modify the collection returned by this method will result in an UnsupportedOperationException.
You can use hasChallengeParameters() to see if a value was sent in this field.
InitiateAuth response if you need
to pass another challenge. The responses in this parameter should be used to compute inputs to the next
call (RespondToAuthChallenge).
All challenges require USERNAME and SECRET_HASH (if applicable).
public final AuthenticationResultType authenticationResult()
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, ChallengeName,
ChallengeParameters, and Session are returned.
ChallengeName, ChallengeParameters, and Session are returned.public InitiateAuthResponse.Builder toBuilder()
toBuilder in interface ToCopyableBuilder<InitiateAuthResponse.Builder,InitiateAuthResponse>toBuilder in class AwsResponsepublic static InitiateAuthResponse.Builder builder()
public static Class<? extends InitiateAuthResponse.Builder> serializableBuilderClass()
public final int hashCode()
hashCode in class AwsResponsepublic final boolean equals(Object obj)
equals in class AwsResponsepublic final boolean equalsBySdkFields(Object obj)
equalsBySdkFields in interface SdkPojopublic final String toString()
public final <T> Optional<T> getValueForField(String fieldName, Class<T> clazz)
getValueForField in class SdkResponseCopyright © 2021. All rights reserved.