You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// The name of the event that triggered the Lambda function.
68
+
///
69
+
/// For a description of each triggerSource see Connecting Lambda triggers to user pool functional operations. https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html#cognito-user-identity-pools-working-with-aws-lambda-trigger-sources
70
+
publiclettriggerSource:TriggerSource
71
+
72
+
/// The AWS Region as an AWSRegion instance.
73
+
publicletregion:AWSRegion
74
+
75
+
/// The ID of the user pool.
76
+
publicletuserPoolId:String
77
+
78
+
/// The current user's username.
79
+
publicletuserName:String
80
+
81
+
/// Metadata about the request and the code environment.
82
+
publicletcallerContext:CallerContext
33
83
}
34
84
35
-
casepreSignUpSignUp(Parameters,PreSignUp)
85
+
casepreSignUp(Parameters,PreSignUp)
36
86
37
87
publicstructPreSignUp:Codable,Hashable,Sendable{
38
88
/// One or more name-value pairs representing user attributes. The attribute names are the keys.
39
89
publicletuserAttributes:[String:String]
90
+
40
91
/// One or more name-value pairs containing the validation data in the request to register a user.
41
92
///
42
93
/// The validation data is set and then passed from the client in the request to register a user. You can pass this data to your Lambda function by using the ClientMetadata parameter in the InitiateAuth and AdminInitiateAuth API actions.
43
94
publicletvalidationData:[String:String]?
95
+
44
96
/// One or more key-value pairs that you can provide as custom input to the Lambda function that you specify for the pre sign-up trigger.
45
97
///
46
98
/// You can pass this data to your Lambda function by using the ClientMetadata parameter in the following API actions: AdminCreateUser, AdminRespondToAuthChallenge, ForgotPassword, and SignUp.
47
99
publicletclientMetadata:[String:String]?
48
100
}
49
101
102
+
case postConfirmation(Parameters,PostConfirmation)
/// One or more key-value pairs representing user attributes.
106
+
publicletuserAttributes:[String:String]
107
+
108
+
/// One or more key-value pairs that you can provide as custom input to the Lambda function that you specify for the post confirmation trigger.
109
+
///
110
+
/// You can pass this data to your Lambda function by using the ClientMetadata parameter in the following API actions: AdminConfirmSignUp, ConfirmForgotPassword, ConfirmSignUp, and SignUp.
111
+
publicletclientMetadata:[String:String]?
112
+
}
113
+
114
+
case postAuthentication(Parameters,PostAuthentication)
/// This flag indicates if the user has signed in on a new device. Amazon Cognito only sets this flag if the remembered devices value of the user pool is Always or User Opt-In.
118
+
publicletnewDeviceUsed:Bool
119
+
120
+
/// One or more name-value pairs representing user attributes.
121
+
publicletuserAttributes:[String:String]
122
+
123
+
/// One or more key-value pairs that you can provide as custom input to the Lambda function that you specify for the post authentication trigger.
124
+
///
125
+
/// To pass this data to your Lambda function, you can use the ClientMetadata parameter in the AdminRespondToAuthChallenge and RespondToAuthChallenge API actions.
126
+
/// Amazon Cognito doesn't include data from the ClientMetadata parameter in AdminInitiateAuth and InitiateAuth API operations in the request that it passes to the post authentication function.
/// A string for you to use as the placeholder for the verification code in the custom message.
134
+
publicletcodeParameter:String?
135
+
136
+
/// The user name. Amazon Cognito includes this parameter in requests that result from admin-created users.
137
+
publicletusernameParameter:String?
138
+
139
+
/// One or more name-value pairs representing user attributes.
140
+
publicletuserAttributes:[String:String]
141
+
142
+
/// One or more key-value pairs that you can provide as custom input to the Lambda function that you specify for the custom message trigger.
143
+
///
144
+
/// The request that invokes a custom message function doesn't include data passed in the ClientMetadata parameter in AdminInitiateAuth and InitiateAuth API operations. To pass this data to your Lambda function, you can use the ClientMetadata parameter in the following API actions:
/// The custom SMS message to be sent to your users. Must include the codeParameter value that you received in the request.
275
+
publicletsmsMessage:String?
276
+
277
+
/// The custom email message to send to your users. You can use HTML formatting in the emailMessage parameter. Must include the codeParameter value that you received in the request as the variable {####}.
0 commit comments