@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 that you're responding to with this call.
|
String |
challengeNameAsString()
The name of the challenge that you're 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()
For responses, this returns true if the service returned a value for the ChallengeParameters property.
|
int |
hashCode() |
List<SdkField<?>> |
sdkFields() |
static Class<? extends InitiateAuthResponse.Builder> |
serializableBuilderClass() |
String |
session()
The session that should pass both ways in challenge-response calls to the service.
|
InitiateAuthResponse.Builder |
toBuilder() |
String |
toString()
Returns a string representation of this object.
|
responseMetadata
sdkHttpResponse
clone, finalize, getClass, notify, notifyAll, wait, wait, wait
copy
public final ChallengeNameType challengeName()
The name of the challenge that you're responding to with this call. This name is returned in the
AdminInitiateAuth
response if you must pass another challenge.
Valid values include the following:
All of the following 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 activated 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.
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 RespondToAuthChallenge.
In a NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that already
has a value. In RespondToAuthChallenge
, set a value for any keys that Amazon Cognito returned in the
requiredAttributes
parameter, then use the UpdateUserAttributes
API operation to modify
the value of any additional attributes.
MFA_SETUP
: For users who are required to setup 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
. 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, an administrator should help the user to add a phone number to their account, and then the user should 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 must pass another challenge.
Valid values include the following:
All of the following 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 activated 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.
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 RespondToAuthChallenge.
In a NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that
already has a value. In RespondToAuthChallenge
, set a value for any keys that Amazon Cognito
returned in the requiredAttributes
parameter, then use the UpdateUserAttributes
API operation to modify the value of any additional attributes.
MFA_SETUP
: For users who are required to setup 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
. 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, an administrator should help the user to add a phone number to their account,
and then the user should call InitiateAuth
again to restart sign-in.
ChallengeNameType
public final String challengeNameAsString()
The name of the challenge that you're responding to with this call. This name is returned in the
AdminInitiateAuth
response if you must pass another challenge.
Valid values include the following:
All of the following 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 activated 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.
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 RespondToAuthChallenge.
In a NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that already
has a value. In RespondToAuthChallenge
, set a value for any keys that Amazon Cognito returned in the
requiredAttributes
parameter, then use the UpdateUserAttributes
API operation to modify
the value of any additional attributes.
MFA_SETUP
: For users who are required to setup 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
. 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, an administrator should help the user to add a phone number to their account, and then the user should 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 must pass another challenge.
Valid values include the following:
All of the following 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 activated 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.
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 RespondToAuthChallenge.
In a NEW_PASSWORD_REQUIRED
challenge response, you can't modify a required attribute that
already has a value. In RespondToAuthChallenge
, set a value for any keys that Amazon Cognito
returned in the requiredAttributes
parameter, then use the UpdateUserAttributes
API operation to modify the value of any additional attributes.
MFA_SETUP
: For users who are required to setup 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
. 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, an administrator should help the user to add a phone number to their account,
and then the user should call InitiateAuth
again to restart sign-in.
ChallengeNameType
public final String session()
The session that should pass both ways in challenge-response calls to the service. If 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 RespondToAuthChallenge
API call.
RespondToAuthChallenge
API call.public final boolean hasChallengeParameters()
isEmpty()
method on the property).
This is useful because the SDK will never return a null collection or map, but you may need to differentiate
between the service returning nothing (or null) and the service returning an empty collection or map. For
requests, this returns true if a value for the property was specified in the request builder, and false if a
value was not specified.public final Map<String,String> challengeParameters()
The challenge parameters. These are returned in the InitiateAuth
response if you must 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.
This method will never return null. If you would like to know whether the service returned this field (so that
you can differentiate between null and empty), you can use the hasChallengeParameters()
method.
InitiateAuth
response if you must 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 result 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.
ChallengeName
, ChallengeParameters
, and Session
are returned.public InitiateAuthResponse.Builder toBuilder()
toBuilder
in interface ToCopyableBuilder<InitiateAuthResponse.Builder,InitiateAuthResponse>
toBuilder
in class AwsResponse
public static InitiateAuthResponse.Builder builder()
public static Class<? extends InitiateAuthResponse.Builder> serializableBuilderClass()
public final int hashCode()
hashCode
in class AwsResponse
public final boolean equals(Object obj)
equals
in class AwsResponse
public final boolean equalsBySdkFields(Object obj)
equalsBySdkFields
in interface SdkPojo
public final String toString()
public final <T> Optional<T> getValueForField(String fieldName, Class<T> clazz)
getValueForField
in class SdkResponse
Copyright © 2023. All rights reserved.