Develop Reference

redirect_uri_mismatch When using OAuth

Im not sure why but when trying to use the following code I get ('Access blocked: This app’s request is invalid' and 'redirect_uri_mismatch') when the browser window opens:
gc = gspread.oauth(
credentials_filename='auth/oauth_creds.json'
)
I have already enabled the needed apis and download the creds for the OAuth client IDs, not sure why I am hitting this error, this is my first time using gspread, in the past I used the normal libs that gspread seems to wrap, but it has been a while.

Redirect uri miss match is one of the most common Oauth2 errors. The redirect uri you have entered in google cloud console for your app must exactly match the one that your application is sending from.
There should be an error details link you can click on it will tell you the exactly redirect uri you should enter into google developer console.
Google OAuth2: How the fix redirect_uri_mismatch error. Part 2 server sided web applications.

How to secure my Azure WebApp with the built-in authentication mechanism

I created a Flask-Webservice with Python that runs independently inside a docker container. I then uploaded the docker image to an Azure Container Registry. From there I can create a WebService (for Containers) with some few clicks in the Azure Portal, that runs this container. So far so good. It behaves just as I want it to.
But of course I don't want anyone to access the service. So I need some kind if authentication. Luckily (or so I thought) there is a built-in authentication-mechanism (I think it is based on OAuth ... I am not that well versed in security issues). Its documentation is a bit sparse on what actually happens and also concentrates on solutions in C#.
I first created a project with Google as described here and then configured the WebApp-Authentication with the Client-Id and Secret. I of course gave Google a java script source and callback-url, too.
When I now log off my Google account and try a GET-Request to my Webservice in the Browser (the GET should just return a "hello world"-String), I am greeted with a Login Screen ... just as I expected.
When I now login to Google again, I am redirected to the callback-url in the browser with some kind of information in the parameters.
a token perhaps? It looks something like this:
https://myapp.azurewebsites.net/.auth/login/google/callback?state=redirxxx&code=xxx&authuser=xxx&session_state=xxx&prompt=xxx).
Here something goes wrong, because an error appears.
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx.
As far as I now, nginx is a server software that hosts my code. I can imagine that it also should handle the authentication process. It obviously lets all requests through to my code when authentication is turned off, but blocks un-authenticated accesses otherwise and redirects to the google login. Google then checks if your account is authorized for the application and redirects you to the callback with the access token along with it. This then returns a cookie which should grant my browser access to the app. (I am just reproducing the documentation here).
So my question is: What goes wrong. Does my Browser not accept the cookie. Did I something wrong when configuring Google+ or the Authentication in the WebApp. Do I have to use a certain development stack to use the authentication. Is it not supported for any of the technologies I use (Python, Flask...).
EDIT
#miknik:
In Microsofts documentation of the authentication/authorization it says
The authentication and authorization module runs in the same sandbox
as your application code. When it's enabled, every incoming HTTP
request passes through it before being handled by your application
code.
...
The module runs separately from your application code and is
configured using app settings. No SDKs, specific languages, or changes
to your application code are required.
So while you are probably right that the information in the callback-redirect is the authorization grant/code and that after that this code should now be used to get an access token from Google, I don't quite understand how this would work in my situation.
As far as I can see it Microsofts WebApp for Container-Resource on Azure should take care of getting the token automatically and return it as part of the response to the callback-request. The documentation states 4 steps:
Sign user in: Redirects client to /.auth/login/.
Post-authentication: Provider redirects client to /.auth/login//callback.
Establish authenticated session: App Service adds authenticated cookie to response.
Serve authenticated content: Client includes authentication cookie in subsequent requests (automatically handled by browser).
It seems to me that step 2 fails and that that would be exactly what you wrote: that the authorization grant is to be used by the server to get the access token but isn't.
But I also don't have any control over that. Perhaps someone could clear things up by correcting me on some other things:
First I can't quite figure out which parts of my problem represent which role in the OAuth-scheme.
I think I am the Owner, and by adding users to the list in the Google+-Project I authorize them to use my service.
Google is obviously the authorization server
my WebService (or better yet my WebApp for Containers) is the resource server
and finally an application or postman that does the requests is the Client
In the descriptions of OAuth I read the problematic step boils down to: the resource server gets the access token from the authorization server and passes it along to the client. And Azures WebApps Resource is prompted (and enabled) to do so by being called with the callback-url. Am I right somewhere in this?
Alas, I agree that I don't quite understand the whole protocol. But I find most descriptions on the net less than helpful because they are not specific to Azure. If anyone knows a good explanation, general or Azure-specific, please make a comment.

I found a way to make it work and I try to explain what went wrong as good as I can. Please correct me if I go wrong or use the wrong words.
As I suspected the problem wasn't so much that I didn't understand OAuth (or at least how Azure manages it) but the inner workings of the Azure WebApp Service (plus some bad programming on my part). Azure runs an own Server and is not using the built-in server of flask. The actual problem was that my flask-program didn't implement a WSGI-Interface. As I could gather this is another standard for python scripts to interact with any server. So while rudimentary calls from the server (I think Azure uses nginx) were possible, more elaborate calls, like the redirect to the callback url went to dev/null.
I build a new app following this tutorial and then secured it by following the authentication/authorization-tutorial and everything worked fine. The code in the tutorial implements WSGI and is probably more conform to what Azure expects. My docker solution was too simple.
My conclusion: read up on this WSGI-standard that flask always warned me about and I didn't listen and implement it in any code that goes beyond fiddeling around in development.

Enabling server side offline access to Google API from iOS app

I am trying to enable server side offline access to Google APIs where the user authenticates from an iOS app. This is to allow a server to have continual access to Google APIs outside of the iOS app.
Google documents the approach below:
https://developers.google.com/identity/sign-in/ios/offline-access
I've followed their documentation exactly with a barebones project. However, whenever I try to exchange the one-time authorization code for access and refresh tokens, I receive a 'redirect_uri_mismatch' error during the exchange.
I've searched forums and a number of folks recommended to configure the Google API project OAuth 2.0 client ID (from Google developer console) with no redirect URIs. However this causes the error 'Missing property "redirect_uris" in a client type of "web"'
I've also tried other OAuth 2.0 client ID types (e.g., Other) but with no luck.
Has anyone been able to get this flow to work? Any help would be greatly appreciated!

I've bumped into this also. Google's example is wrong or at least incomplete. You have to set a redirect uri on the developer console and pass it to the oauth client like so:
credentials = client.credentials_from_clientsecrets_and_code(
CLIENT_SECRET_FILE,
['https://www.googleapis.com/auth/drive.appdata', 'profile', 'email'],
auth_code, None, "your redirect uri")
Full documentation here http://oauth2client.readthedocs.io/en/latest/source/oauth2client.client.html

Set redirect_uri to urn:ietf:wg:oauth:2.0:oob in your code, it is used for installed app. As mentioned by #oravecz over here. This worked for me.

With Google App Engine, is it possible to customize boilerplate in default user authorization template?

I'm referring to the page at https://appengine.google.com/_ah/loginform that the user will be redirected to by the users.create_login_url method from the google.appengine.api module. This is for authentication using Google Accounts.
I'd like to change references to the project name (which is different from my custom domain) to match my domain.
The page currently says:
The application project-name is requesting permission to access your Google Account.
I'd prefer it said:
The application example.com is requesting permission to access your Google Account.
I've updated the settings in the Google Cloud Platform dashboard under API Manager > Credentials > OAuth Consent Screen, but (even a couple hours later) that doesn't seem to have had any impact.
I've searched the App Engine settings in the dashboard as well. Is this possible? If not, suggestions for a workaround?
Update
I've opened up an issue (Issue 12919) on Google Code as suggested by #DanCornilescu below. It references both this question and the other recent StackOverflow question related to this issue.
I also raised the issue on Reddit in the AppEngine subreddit. The Google dev marked the Google Code ticket private so I could upload some private project information, but I'll update its status in the Reddit thread.
Workaround
#steeling's answer below offers a workaround that worked for me.

There's a bug here, but in the meantime you can go through the old admin console at appengine.google.com. If you click "Application Settings" after clicking on your application it will take you to the new cloud console. But if you right click and copy the link and remove the "&deprecated" at the end of the url you can still visit the old page.

There's currently a bug where changes to the project title are not getting synced to App Engine after you create the application.
This is definitely a bug, and we're working on figuring out what broke this sync.

Error in Tutorial to sign-in to Google account using Python

This is a direct follow up to the information provided in this question:
Enter website by logging in Google Account using Python
One of the suggestions I found, was to follow this google tutorial for python:
quick start for python
And I am having some problems because of the heavy changes in the interface.
My biggest problem is in Step 1 - 3b. Aparently I have to paste these values:
http://localhost:4567
http://mysite.example.com
https://mysite.example.com
in some place, but I have no idea where.
So I simply continued with the tutorial, and launched the application on my localhost on port 4567.
Now, the application launched fine, but when I click the login button I get an error:
Error:invalid_client
no registered origin
Request details:
scope=https://www.googleapis.com/auth/plus.login https://www.googleapis.com/auth/plus.moments.write https://www.googleapis.com/auth/plus.me https://www.googleapis.com/auth/plus.profile.agerange.read https://www.googleapis.com/auth/plus.profile.language.read https://www.googleapis.com/auth/plus.circles.members.read
redirect_uri=postmessage
state=303270744|0.3942616991
origin=http://localhost:4567
display=page
request_visible_actions=http://schemas.google.com/AddActivity
cookie_policy_enforce=false
response_type=code token id_token gsession
access_type=offline
cookie_policy=single_host_origin
proxy=oauth2relay678941372
client_id=933139289991-iigr70l8u8rbjecm6vrrs3bj4fck0ptu.apps.googleusercontent.com
authuser=0
Am I getting this error because the tutorial I am following is very outdated, or because I didn't do Step 1 - 3b correctly?
How can I fix this? All I want is to log in into a google account, if there is an easier way to do it with python, feel free to let me know :S

The problem is that the tutorial tells you how to set up the project using the Google API Console (see the link in Step 1, the first item), but Google is slowly moving people to use the Cloud Console instead. So if you follow that link, you get redirected to the new Cloud Console. If you want to get back to the API Console (so you can follow the rest of the steps listed there), you should see a message at the top of that page that says:
If you click on the "Go back" link, you'll be back at the API Console and you can follow the rest of the steps listed in the tutorial.
Steps 1-3b are important, since they are how you setup a Project, indicate what API resources it has available to it, and indicate how you will be accessing the project. It also will give you the Client ID and Secret that your python program will use when connecting to Google's servers.