Skip to content
This repository has been archived by the owner on May 19, 2021. It is now read-only.

Custom Authorizer #20

Closed
dhiman-halder opened this issue May 15, 2016 · 1 comment
Closed

Custom Authorizer #20

dhiman-halder opened this issue May 15, 2016 · 1 comment

Comments

@dhiman-halder
Copy link

dhiman-halder commented May 15, 2016

Now that AWS API Gateway has introduced Custom Authorizer, does the approach described here change in anyway ?

@sapessi
Copy link
Contributor

sapessi commented Jul 14, 2016

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants