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
Maintenance: graduate the Auth utility from auth_alpha to auth #8816
The Auth utility shipped as auth_alpha in 3.36.0 (#8469 for JWT verification, #8486 for the OAuth2 client, from the RFCs #8466 and #8489). Seven releases later the API has not moved, we have no open bug on it, and people are using it in production despite the warning in the docs. Time to graduate it.
What changes
New namespace aws_lambda_powertools.utilities.auth, with the same public surface: JWTVerifier, OAuth2Client, AuthErrorContext, AuthFailureReason and the exceptions.
aws_lambda_powertools.utilities.auth_alpha stays as an alias that re-exports everything and emits a PowertoolsDeprecationWarning on import. It goes away in v4, per our compatibility policy.
Docs: Auth (alpha) and OAuth2 client (alpha) lose the alpha title and the warning admonition; examples move from examples/auth_alpha/ to examples/auth/; the API reference entry follows.
The extra stays jwt, nothing changes for pip install aws-lambda-powertools[jwt].
The agent skill reference is regenerated with the release, as usual now.
Why now
I want to add request signing (SigV4) to this utility, see #8817. I would rather land that on a stable auth namespace than add a second alpha surface next to the first one. So the order is: this issue first, the signer right after.
Out of scope
No behaviour change in JWTVerifier or OAuth2Client. If you have an API change you think must happen before GA, say it here now, this is the last call.
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
powertools-for-aws-oss-automation commentedon Nov 15, 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.