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 }}
This repository has been archived by the owner on May 19, 2021. It is now read-only.
No. Sigv4 continues to work exactly as it did before. Customer authorizers allow you to leverage bearer tokens such as JWT tokens or SAML assertions. It's an alternative approach.
Now that AWS API Gateway has introduced Custom Authorizer, does the approach described here change in anyway ?
The text was updated successfully, but these errors were encountered: