I'm hoping someone on this list has encountered this, and can say "Yeah, I ran 
into that. Here's how I dealt with it..."

I'm looking for an easy step-by-step guide to just get the exact behavior that 
Python 2.7 had.

-Joshua

> On Jan 25, 2021, at 1:05 PM, 'Elliott (Cloud Platform Support)' via Google 
> App Engine <[email protected]> wrote:
> 
> Hello Joshua,
> 
> I understand that you would like an easy way to implement authentication 
> because you may not continue to use login: admin. I was able to confirm this. 
> First, I would like to apologize for the inconvenience. There is no easy way 
> other than to implement one of the options listed in this document 
> <https://cloud.google.com/appengine/docs/standard/python3/authenticating-users>.
> 
> You are presented with some options including Firebase Authentication, Google 
> Sign-In and OAuth 2.0 and OpenID Connect. Each of these technologies are 
> described in the document.
> 
> I would like your thoughts on the recommended ways so that we may find a 
> solution that agrees with you.
> 
> I hope that we may now have enough to elaborate on this discussion.
> 
> 
> On Friday, January 22, 2021 at 1:07:16 PM UTC-5 Joshua Smith wrote:
> In my quest to figure out how to keep using Google App Engine when Python27 
> eventually goes away, I've just run into yet another case where something 
> simple seems to have been replaced with a nightmare of complexity 
> <https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3/migrating-services#user_authentication>.
> 
> In my old app.yaml, I had this:
> 
> - url: /admin/.*
>   script: main.app
>   secure: always
>   login: admin
> 
> Unfortunately, python37 doesn't support login: admin any more (!). I'm facing 
> a mountain of documentation detailing a bunch of different ways I can do 
> authentication now.
> 
> Stack overflow is no help at all in simplifying this.
> 
> Anyone here have advice on the easiest possible way to get the old Python27 
> behavior that you have to be logged in as the app administrator in order to 
> hit a certain URL?
> 
> This isn't for ensuring crons are only run by cron. That seems pretty easy by 
> looking at headers.
> 
> This is for when you have administrative functions that only the developers 
> need access to, and I'm looking for the easiest way to ensure a URL is only 
> accessible to those particular people.
> 
> In case it matters, I'm using Flask.
> 
> -Joshua
> 
> 
> -- 
> 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] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/05ac62c4-6c44-4e7b-8068-1601d6a4eef0n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/google-appengine/05ac62c4-6c44-4e7b-8068-1601d6a4eef0n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
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/90827D18-4CCA-407F-92D4-3C2485FC0EBE%40gmail.com.

Reply via email to