harmit is right, but at a fairly low level. i've encapsulated the oauth 
implementations for lots of existing social sites and integrated them with 
app engine in the oauth-dropins package. feel free to try it out: 
https://oauth-dropins.appspot.com/ . if you like it, you can pip install it 
into your app's virtualenv and use it from there. more details in the docs: 
https://oauth-dropins.readthedocs.io/

On Monday, July 8, 2019 at 11:59:51 AM UTC-7, Harmit Rishi (Cloud Platform 
Support) wrote:
>
> Hello, 
>
> Thank you for using Google Groups!
>
> Based on my understanding of what you have described, you can implement 
> OAuth within Google App engine. You may find further details of this here 
> <https://cloud.google.com/appengine/docs/standard/python/oauth/#oauth_20_and_openid_connect>.
>  
>
>
> However, I was able to find *StackOverflow* threads that revolve around 
> this issue with Webapp2. In regards to specific social logins, I was able 
> to find the following thread here 
> <https://stackoverflow.com/questions/25678594/integrate-facebook-login-in-google-app-engine-with-python>
>  that 
> discusses how to integrate Facebook login within App Engine. Though, I 
> believe it would be worthwhile for you to check out the discussion here 
> <https://stackoverflow.com/questions/7641110/webapp2-for-authentication-and-login>
>  as 
> the entire thread discusses "Webapp2 Authentication and Login". 
> Additionally, there is a third party boilerplate provided by the community 
> on that thread for what you are attempting to do. You may feel free to 
> explore the links shared to determine if the ideas discussed in them would 
> be applicable in your use case.
>
> I hope this helps!
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/00426117-a13e-4396-813a-b4e4190550b8%40googlegroups.com.

Reply via email to