You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug: TransferFamilyAuthorizer.password raises KeyError when the event has no password #8714
TransferFamilyAuthorizer.password is typed str | None and documented as "None in case customer authenticating with certificates", so an authorizer event without a password should give None. The Pydantic TransferFamilyAuthorizer model already declares password with default=None.
Current Behaviour
The property returns self["password"], so an event without a password key raises KeyError instead of returning None. The custom identity provider examples in the Transfer Family docs read it defensively (event.get('password', '') == '' in Python) to detect key-based logins, which the data class can't do today.
Thanks @anishmehta24, confirmed. Transfer Family leaves password out for key-based logins and we blow up with KeyError instead of returning None like the type hint says. I'll review #8715. Goes into 3.40.0.
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Activity
leandrodamascena commentedon Oct 30, 2026
Thanks @anishmehta24, confirmed. Transfer Family leaves
passwordout for key-based logins and we blow up withKeyErrorinstead of returningNonelike the type hint says. I'll review #8715. Goes into 3.40.0.leandrodamascena commentedon Nov 4, 2026
Fixed by #8715, merged as c8da226.
powertools-for-aws-oss-automation commentedon Nov 4, 2026
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
github-actions commentedon Nov 10, 2026
This is now released under 3.40.0 version!