Feature request: Parser PostAuthentication_Authentication Schema

[AlessandroVol23]

Use case

Hey 👋🏽

I'm missing a schema for the trigger PostAuthentication_Authentication

Solution/User Experience

Add schema for PostAuthentication_Authentication trigger

Alternative solutions

Acknowledgment

• This feature request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[dreamorosi]

Hi @AlessandroVol23, thank you for opening this issue.

Similar to #4803, could you please share an example of the payload you're missing or a link to the docs that we can use as reference?

Thank you.

[dreamorosi]

On second thought, I looked at the Post authentication Lambda trigger docs and compared them with our existing schemas.

It turns out we already have PostAuthenticationTriggerSchema which handles the PostAuthentication_Authentication trigger source:

import { PostAuthenticationTriggerSchema } from '@aws-lambda-powertools/parser/schemas';

The schema includes all the fields from the AWS documentation:

• triggerSource (literal 'PostAuthentication_Authentication')
• userPoolId, userName, callerContext (from base schema)
• request.userAttributes
• request.newDeviceUsed (optional)
• request.clientMetadata (optional)

You can see the implementation here: https://github.com/aws-powertools/powertools-lambda-typescript/blob/main/packages/parser/src/schemas/cognito.ts#L178-L185

Is there something specific missing from this schema that you need, or does this address your use case?

[github-actions]

This issue has not received a response in 2 weeks. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.

[github-actions]

Greetings! We are closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or reopen the issue.