serverless-authentication-boilerplate
serverless-authentication-boilerplate copied to clipboard
laardee
Generic authentication boilerplate for Serverless framework
Hello, I got error on google provider. ``` Legacy People API has not been used in project xxx before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/legacypeople.googleapis.com/overview?project=xxx then retry....
This update changes custom-google.js to accommodate changes to Google's plus API no longer being available.
Hello, This works great on the web. But it would be cool with a boilerplate for a "mobile app". Where you don't use the redirect flows. Cause that's usually handled...
This looks great for authorizing with different providers through an intermediary service, and setting up the endpoints to do so! However, for using the auth-result of this with any other...
I don't understand why is it necessary? I leave "token-secret-123" and my project works prefect, so how it works?
Is it planned to get typings support (with TypeScript) on this library?
This makes the sign in handler propagate errors like other handlers.
Would be good if you could document exactly how to fill in **PROVIDER_GOOGLE_ID** & **PROVIDER_GOOGLE_SECRET**.
