@Generated(value="software.amazon.awssdk:codegen") public final class AdminInitiateAuthResponse extends CognitoIdentityProviderResponse implements ToCopyableBuilder<AdminInitiateAuthResponse.Builder,AdminInitiateAuthResponse>
Initiates the authentication response, as an administrator.
Modifier and Type | Class and Description |
---|---|
static interface |
AdminInitiateAuthResponse.Builder |
Modifier and Type | Method and Description |
---|---|
AuthenticationResultType |
authenticationResult()
The result of the authentication response.
|
static AdminInitiateAuthResponse.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 AdminInitiateAuthResponse.Builder> |
serializableBuilderClass() |
String |
session()
The session that should be passed both ways in challenge-response calls to the service.
|
AdminInitiateAuthResponse.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 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. This challenge should be passed with NEW_PASSWORD
and any other required attributes.
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.
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.
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. This challenge should be passed with NEW_PASSWORD
and any other required
attributes.
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.
ChallengeNameType
public final String challengeNameAsString()
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. This challenge should be passed with NEW_PASSWORD
and any other required attributes.
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.
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.
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. This challenge should be passed with NEW_PASSWORD
and any other required
attributes.
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.
ChallengeNameType
public final String session()
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.
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.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 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.
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.
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.
public final AuthenticationResultType authenticationResult()
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.
ChallengeName
, ChallengeParameters
, and Session
are returned.public AdminInitiateAuthResponse.Builder toBuilder()
toBuilder
in interface ToCopyableBuilder<AdminInitiateAuthResponse.Builder,AdminInitiateAuthResponse>
toBuilder
in class AwsResponse
public static AdminInitiateAuthResponse.Builder builder()
public static Class<? extends AdminInitiateAuthResponse.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 © 2022. All rights reserved.