ResendConfirmationCodeRequest (p.awso.0.9.1.doc.awso.cognito-idp.Awso_cognito

Sourcetype nonrec t = {

clientId : ClientIdType.t;
(*
The ID of the user pool app client where the user signed up.
*)
secretHash : SecretHashType.t option;
(*
A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message. For more information about SecretHash, see Computing secret hash values.
*)
userContextData : UserContextDataType.t option;
(*
Contextual data about your user session like the device fingerprint, IP address, or location. Amazon Cognito threat protection 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. For more information, see Collecting data for threat protection in applications.
*)
username : UsernameType.t;
(*
The name of the user that you want to query or modify. The value of this parameter is typically your user's username, but it can be any of their alias attributes. If username isn't an alias attribute in your user pool, this value must be the sub of a local user or the username of a user from a third-party IdP.
*)
analyticsMetadata : AnalyticsMetadataType.t option;
(*
Information that supports analytics outcomes with Amazon Pinpoint, including the user's endpoint ID. The endpoint ID is a destination for Amazon Pinpoint push notifications, for example a device identifier, email address, or phone number.
*)
clientMetadata : ClientMetadataType.t option;
(*
A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers. You create custom workflows by assigning Lambda functions to user pool triggers. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute that provides the data that you assigned to the ClientMetadata parameter in your request. In your function code, you can process the clientMetadata value to enhance your workflow for your specific needs. To review the Lambda trigger types that Amazon Cognito invokes at runtime with API requests, see Connecting API actions to Lambda triggers in the Amazon Cognito Developer Guide. When you use the ClientMetadata parameter, note that Amazon Cognito won't do the following: Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn't include triggers, the ClientMetadata parameter serves no purpose. Validate the ClientMetadata value. Encrypt the ClientMetadata value. Don't send sensitive information in this parameter.
*)

}

Sourceval context_ : string

val make : 
  ?secretHash:??? ->
  ?userContextData:??? ->
  ?analyticsMetadata:??? ->
  ?clientMetadata:??? ->
  clientId:ClientIdType.t ->
  username:UsernameType.t ->
  unit ->
  t

Source

val to_value : 
  t ->
  [> `Structure of
       (string
        * [> `Map of
               ([> `String of StringType.t ] * [> `String of StringType.t ])
                 list
          | `String of ClientIdType.t
          | `Structure of (string * [> `String of StringType.t ]) list ])
         list ]

Sourceval to_query : t -> Awso.Client.Query.t

Sourceval of_xml : Awso.Xml.t -> t

Sourceval of_string : string -> t

Sourceval of_json : Yojson.Safe.t -> t

Sourceval to_json : t -> Yojson.Safe.t