Skip to content
#

oauth2

Here are 638 public repositories matching this topic...

express-gateway
XVincentX
XVincentX commented Jan 2, 2018

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

kotodharma
kotodharma commented Jun 11, 2017

I'm fascinated by your claim that this is a simple, decentralized, software-only solution to the Authentication Problem that somehow you have solved where lots of other smart and highly-trained people have failed. You must forgive me if I'm a bit skeptical. I've seen your readme here, and your blog post, and you have given us a lot of bold claims, and some code, and a flow diagram. I don't feel li

jchris
jchris commented Mar 23, 2017

Here are 3 sequence diagrams of how this works, that you can plug into https://www.websequencediagrams.com/ when you are making slides or whatever.

title Authentication
Browser->Sign In: Initial request
Sign In -> Facebook: Redirect
note over Facebook: Approve login
Facebook -> Callback: Redirect
Callback -> FaunaDB: Find or create user
FaunaDB -> Callback: Database secret for user

Improve this page

Add a description, image, and links to the oauth2 topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the oauth2 topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.