[Manishram-ai]

Issue number:
closes #8761

Summary

Changes

• CognitoChallengeResultModel.challengeName accepts CUSTOM_CHALLENGE, the first challenge type in the define auth challenge docs.
• The pre sign-up, post confirmation, custom email sender and custom SMS sender models accept every triggerSource documented for their trigger. The lists come from the trigger sources reference and the custom email and custom SMS sender pages. The trigger sources reference spells the SMS sources CustomSmsSender_*, but the custom SMS sender page and the API table use CustomSMSSender_*, which matches the existing literal, so I kept that spelling.
• answerCorrect in the verify auth challenge response and callerContext.clientId are optional, because Cognito sends null for both. The function sets answerCorrect, and admin API calls such as AdminConfirmSignUp have no client ID.
• New tests cover each newly accepted trigger source, CUSTOM_CHALLENGE in the define and create auth challenge sessions, and the two null values. Each one starts from the existing fixture and changes one field.

This is the same fix as aws-powertools/powertools-lambda-typescript#5777. Python's session has no minimum length and its custom sender models don't require response, so those two parts of the TypeScript change weren't needed here.

User experience

Today a custom auth flow can't be parsed past its first custom challenge, verify auth challenge events fail on answerCorrect, and pre sign-up, post confirmation and custom sender events from admin, federated, forgot password and resend code flows fail with a ValidationError. With this change they parse, and handlers can branch on triggerSource and challengeName the way the Cognito docs describe.

Verification

• The 20 new test cases fail on develop and pass with this change.
• tests/unit/parser, tests/functional/parser and tests/unit/data_classes: 449 passed (Python 3.12).
• ruff format --check and ruff check are clean on the changed files, and mypy shows no errors in cognito.py.
• I didn't run these against a live user pool. The trigger sources and CUSTOM_CHALLENGE come from the Cognito docs, and the two null values come from the events captured from a live user pool in Bug: Cognito trigger schemas reject real events from common flows powertools-lambda-typescript#5770.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud