Google Endpoints authentication flow with Ferris 3

[Jay Koontz]

Love the new Ferris Framework. Just what I need. One big problem for me, though:

Google Endpoints authentication scheme w/ OAuth2 (my initial primary usage will be through javascript on a website).

Last time I had to deal with this, the result was that my users were REQUIRED to have a Google Account in order to authorize the API endpoints I created.

So instead of just being able to login with the email/pwd combo they signed up with, they were forced into having a GOOGLE account to SEPARATELY "authorize" the endpoints my app uses.

Did I just get it all wrong? Please tell me I got it all wrong.

What are your guys' experience with handling the auth flow? Do your users have their own email/pwd and dont have to worry about separately authorizing the endpoints?

[Ben Adrian Sarmiento]

You are correct, using OAuth2 with Cloud Endpoints requires having a Google account. What you can do instead is make all your endpoints public and use either:

a. OAuth2 with your own identity provider (there are many oauth2 libraries for Python out there)

b. other token-based authentication mechanism like JSON Web Tokens

[Aki Tanaka]

Hi,

Have you tried the Note Example https://github.com/jonparrott/Ferris-Eydis-Notes-Example ?

I dont know how the author wrote the code, but I can see that user is not required o login to post a message.