Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing authenticationTypes OPENID_CONNECT and AWS_LAMBDA support #159

Open
mayunike opened this issue Mar 8, 2022 · 2 comments
Open

Missing authenticationTypes OPENID_CONNECT and AWS_LAMBDA support #159

mayunike opened this issue Mar 8, 2022 · 2 comments

Comments

@mayunike
Copy link

mayunike commented Mar 8, 2022 •
edited
Loading

I see currently authenticationType API_KEY only supported. Any plans to support other authentication types?

Thank you
@mayunike mayunike changed the title Missing support for authenticationType OPENID_CONNECT, AWS_LAMBDA, Missing authenticationTypes OPENID_CONNECT and AWS_LAMBDA support Mar 8, 2022
@katesclau
Copy link
Contributor

This depends on implementation on appsync-cli, more specifically, in the amplify-appsync-simulator package https://github.com/aws-amplify/amplify-cli

I've implemented a quick solution in our forked package (we also use a custom serverless-appsync-simulator forked from this one)
returnmates/amplify-appsync-simulator@7c8535d

I guess the proper way is to open an issue on amplify-cli, and follow up with a PR, but I've gone that path on another issue and their process is too slow for us...

Feel free to pick what you need from our repo 😉

@sambP
Copy link

sambP commented Jan 26, 2023

duplicate #148 , right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sambP @katesclau @mayunike