(aws-apigatewayv2-authorizers): HttpUserPoolAuthorizer constructor should take and array of user pool client ids

[dan-lind]

The current HttpUserPoolAuthorizer is created like this

const authorizer = new HttpUserPoolAuthorizer({
    userPool: userPool,
    userPoolClient: userPoolClient,
});

This will synthesize to

 "MyTestHttpProxyPrivateApiUserPoolAuthorizer":{
   "Type":"AWS::ApiGatewayV2::Authorizer",
   "Properties":{
      "ApiId":{
         "Ref":"MyTestHttpProxyPrivateApi"
      },
      "AuthorizerType":"JWT",
      "Name":"UserPoolAuthorizer",
      "IdentitySource":[
         "$request.header.Authorization"
      ],
      "JwtConfiguration":{
         "Audience":[
            "<user pool id>"
         ],
         "Issuer":"https://cognito-idp.eu-west-1.amazonaws.com/eu-west-1_XXXXXXXXX"
      }
   }
},

Where the provided user pool client id end up in the Audience array

Use Case

Currently it is possible to provide multiple user pool ids using a HttpJwtAuthorizer

const jwtAuthorizer = new HttpJwtAuthorizer({
    jwtAudience: ['XXXXXX', 'YYYYYY'],
    jwtIssuer: `https://cognito-idp.eu-west-1.amazonaws.com/eu-west-1_XXXXXXXXX`
})

For consistency and ease of use, HttpUserPoolAuthorizer should also allow users to pass an array of user pool clients, rather than a single one.

Proposed Solution

Allow users to pass an array of user pool clients like so

const authorizer = new HttpUserPoolAuthorizer({
    userPool: userPool,
    userPoolClient: [userPoolClient1, userPoolClient2, userPoolClient3]
});

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[nija-at]

Thanks for submitting this feature request.

I'm marking this issue as a p2, which means we will not be working on this right away. We are accepting pull requests if you would like to contribute.

[reowl666]

I am also facing this problem.
I can't target multiple app clients and I'm looking for a workaround.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.