Sapisidhash & Clients6 endpoints

[llvmx]

Sapisidhash & Clients6 endpoints

[mxrch]

Hi ! This auth method doesn't specifically bypass any quota limit / restrictions, the only thing is that some APIs / endpoints require this type of auth (with SAPISIDHASH + cookies), meanwhile other require only cookies, or only oauth2.
That's why I have set this parameter on APIs classes :

GHunt/ghunt/apis/peoplepa.py

Line 28 in a158d7a

self.authentication_mode = "sapisidhash" # sapisidhash, cookies_only, oauth or None

[llvmx]

Thanks for the response.
Guess it's true there are still limits since google is limiting per user on their internal projects.
However, I was confused why Sapisidhash is used for the calendar/people API, because oauth would have worked out as well I think.

[mxrch]

Because oauth2 is more relevant in mobile apps.
You first register a device (your phone), then generate a master token and keep on the device.
And with this master token you generate oauth2 tokens for all the apps you want.

The SAPISIDHASH is more appropriate for a browser because it's only a variation of the SAPISID cookie, and these cookies are variable inside the *.google.com scope, so you don't have to do the oauth2 flow for each Google service you're navigating to.