cognitoidentityprovider_get_client_token: Issues an access token for machine-to-machine (M2M)...

In paws.security.identity: 'Amazon Web Services' Security, Identity, & Compliance Services

Issues an access token for machine-to-machine (M2M) authorization

Description

Issues an access token for machine-to-machine (M2M) authorization. Your app client provides its client ID and secret, and receives an access token that authorizes requests to your resource servers.

See https://www.paws-r-sdk.com/docs/cognitoidentityprovider_get_client_token/ for full documentation.

Usage

cognitoidentityprovider_get_client_token(
  ClientId,
  Secret,
  Scopes = NULL,
  ClientMetadata = NULL
)

Arguments

ClientId	[required] The ID of the app client that requests the access token. The app client must have a client secret and the ALLOW_CLIENT_TOKEN_AUTH authentication flow.
Secret	[required] An active secret for the app client.
Scopes	The custom scopes to authorize in the access token, in the format resource-server-identifier/scope-name. Each scope must belong to a resource server in your user pool. If you don't specify any scopes, Amazon Cognito authorizes the scopes that are configured for the app client.
ClientMetadata	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.

paws.security.identity documentation built on Oct. 8, 2026, 9:12 a.m.