How can I decode and verify the signature of an Amazon Cognito JSON Web Token?
I want to use an Amazon Cognito user pool as the authentication method for my application. What is a secure way to verify the ID and access tokens sent by clients to my application?
"I want to use an Amazon Cognito user pool as the authentication method for my application. What is a secure way to verify the ID and access tokens sent by clients to my application?Short descriptionWhen clients authenticate to your application with a user pool, Amazon Cognito sends an ID token. You can manually verify the ID token in scenarios similar to the following:You created a web application and want to use an Amazon Cognito user pool for authentication.You use an Amazon Cognito user pool for authentication and an Amazon Cognito identity pool to retrieve AWS Security Token Service (AWS STS) temporary credentials. AWS Lambda is invoked with those credentials, but Lambda doesn't have information about who originally authenticated with the user pool.To get Amazon Cognito user details contained in an Amazon Cognito JSON Web Token (JWT), you can decode the token and then verify the signature.ResolutionAWS released the following library that you can use to verify JWTs: https://github.com/awslabs/aws-jwt-verifyimport { CognitoJwtVerifier } from "aws-jwt-verify";// Verifier that expects valid access tokens:const verifier = CognitoJwtVerifier.create({  userPoolId: "<user_pool_id>",  tokenUse: "access",  clientId: "<client_id>",});try {  const payload = await verifier.verify(    "eyJraWQeyJhdF9oYXNoIjoidk..." // the JWT as string  );  console.log("Token is valid. Payload:", payload);} catch {  console.log("Token not valid!");}After a user logs in, an Amazon Cognito user pool returns a JWT. The JWT is a base64url-encoded JSON string ("claims") that contains information about the user. Amazon Cognito returns three tokens: the ID token, the access token, and the refresh token. The ID token contains the user fields defined in the Amazon Cognito user pool.Tokens include three sections: a header, a payload, and a signature.The following is the header of a sample ID token. The header contains the key ID ("kid"), as well as the algorithm ("alg") used to sign the token. In this example, the algorithm is "RS256", which is an RSA signature with SHA-256.{  "kid": "abcdefghijklmnopqrsexample=",  "alg": "RS256"}The following is an example of the payload, which has information about the user, as well as timestamps of the token creation and expiration:{  "sub": "aaaaaaaa-bbbb-cccc-dddd-example",  "aud": "xxxxxxxxxxxxexample",  "email_verified": true,  "token_use": "id",  "auth_time": 1500009400,  "iss": "https://cognito-idp.ap-southeast-2.amazonaws.com/ap-southeast-2_example",  "cognito:username": "anaya",  "exp": 1500013000,  "given_name": "Anaya",  "iat": 1500009400,  "email": "anaya@example.com"}The last section is the signature, which is a hashed and encrypted combination of the header and the payload.Amazon Cognito generates two RSA key pairs for each user pool. The private key of each pair is used to sign the respective ID token or access token. The public keys are made available at an address in the following format:https://cognito-idp.{region}.amazonaws.com/{userPoolId}/.well-known/jwks.jsonThe JSON file (jwks.json) is structured in the following format:{    "keys": [{        "alg": "RS256",        "e": "AQAB",        "kid": "abcdefghijklmnopqrsexample=",        "kty": "RSA",        "n": "lsjhglskjhgslkjgh43lj5h34lkjh34lkjht3example",        "use": "sig"    }, {        "alg":        "RS256",        "e": "AQAB",        "kid": "fgjhlkhjlkhexample=",        "kty": "RSA",        "n": "sgjhlk6jp98ugp98up34hpexample",        "use": "sig"    }]}To verify the signature of an Amazon Cognito JWT, first search for the public key with a key ID that matches the key ID in the header of the token. Then, you can use libraries, such as aws-jwt-verify or those recommended by jwt.io or OpenID Foundation, to validate the signature of the token and extract values, such as expiration and user name.Apart from the signature, it's also a best practice to verify the following:The token isn't expired.The audience ("aud") specified in the payload matches the app client ID created in the Amazon Cognito user pool.The aws-jwt-verify library includes these checks on your behalf. For more code examples on how to decode and verify an Amazon Cognito JWT using Lambda, see Decode and verify Amazon Cognito JWT tokens.Related informationVerifying a JSON Web TokenUsing tokens with user poolsFollow"