Improve Google auth docs about confidant HOT 7 CLOSED

Ah, and I did have to enable G+. Sorry if that was not clear.

from confidant.

This is related to some info @damaestro added in the IRC channel. It's necessary to enable the people API for google auth to work, but that's not documented, along with most of the rest of that setup.

from confidant.

So I'm running into the same issue that Jon was having with authentication. I have the Google People API enabled for project / oauth2 client configuration.

While I'm working through figuring out what's going on I found this Google Site:
https://developers.google.com/+/web/api/rest/oauth#authorization-scopes

Which states the scopes you have configured are deprecated.

from confidant.

They are indeed deprecated. In the 1.1 branch we're using the updated scopes:

https://github.com/lyft/confidant/blob/1.1/confidant/authnz/userauth.py#L274-L285

That said, the deprecated scopes do work. What issue are you running into?

from confidant.

@ryan-lane I was having an issue getting the google suffix working. It was throwing a 500 error with "NoneType" attribute when checking against the email address:
AttributeError: 'NoneType' object has no attribute 'endswith'

I added the Google People API to my Google Project and it wasn't fetching. So I searched all the google APIs for userinfo usage. I switched to the Google+ API and it's now working.

As for the deprecated apis yeah Google says they will support them for a while. Just an FYI, good to see it's updated.

from confidant.

Just as an annotation: G+ does have to be enabled.

Note that the exception should ideally be trapped and the error message from google emitted. Something like checking for user.email being None and using logging.error with result.user.data would suffice, internal research shows.

from confidant.

Added some basic google auth docs: #84

from confidant.