google-oauth2

I am trying to use the Google+ sign in button via the javascript api. Everything works fine on Windows computers and Chromebooks, but it fails on every Mac that I have been able to test it on. (see update 2 below, this is not actually a Mac problem) When the initial Google api file is loaded ( https://apis.google.com/js/client:platform.js ) an error is logged in the console, saying that https://accounts.google.com/o/oauth2/iframerpc?scope=email+profile&response_type=token+id_token&login_hint=[HINT]&origin=[ORIGIN]&action=issueToken&ss_domain=[SS_DOMAIN]&hd=[HD]&client_id=[CLIENT_ID]&hl=en&from

Recently we noticed that our app OAuth consent screen does not show Logo and Name of application. Instead, it shows the redirect URL. And there is no Terms and Privacy that we provided in developers console. This is how our OAuth consent screen is setup: Can some one please tell what we are doing wrong? We made some of these changes to respond to the OAuth phishing. These changes were done in a short time so it applies to all apps. The redirect domain shows the real place the token will be sent (vs. the name was not verified and could have been anything). We understand that this impact some

I'm using Google Sign-In JavaScript client for months without problem. But recently when user tapping on sign in button from webapp that added to homescreen, the signin pop-up just hang without showing any content. When debugged via remote debugging, an error is displayed in console pane: Uncaught Failed to get parent origin from URL hash! originated from 4188232449-v2-idpiframe.js:136 (javascript loaded internally by google library). I'm sure it's not programming/config error since the same webapp was previously working for months without problem, and I haven't modified any code. I've tried

I am trying to get a simple Python Google Drive uploader working. I've created a project in the developer console, enabled the Drive API and added an OAuth 2.0 client ID (application type Other). I can see the application listed in the Google Drive's Settings -> Manage Apps, and can successfully execute many operations provided by the Python Drive API client from Google. files ().insert () however fails with: googleapiclient.errors.HttpError: <HttpError 403 when requesting https://www.googleapis.com/upload/drive/v2/files?uploadType=multipart&convert=false&useContentAsIndexableText=false&alt

When I am signing into Gmail in my iOS App, I am getting the below error (screenshot) and the sign-in fields do not appear. We are loading the sign-in screen in a WKWebView. We are using a custom URI redirect but why is google throwing this error now. What are the alternatives to a custom URI? Swift 2.3 project Using OAuthSwift v0.6.0 cocoapod This started quite recently only in the past week or so I believe something changed with Google's APIs. I have read that google is deprecating webviews for OAuth and will block requests on April 20, 2017. As seen here in a Google Developers Blog: https:/

I'm developing an application wherein I need to access multiple google calendars. All these calendars come from different users. And right now I am using OAuth2 for the syncing. But as I understand it, I can only generate 25 refresh tokens per client ID. Note: Save refresh tokens in secure long-term storage and continue to use them as long as they remain valid. Limits apply to the number of refresh tokens that are issued per client-user combination, and per user across all clients, and these limits are different. If your application requests enough refresh tokens to go over one of the limits,

This is a follow-up to a previous question/answer I posted ( How to use the Google Email Settings API and the OAuth2 for Apps Script Library to set email signatures for users in a Google Apps domain ), but I'm creating a new question since the Email Settings API has been deprecated and the process is significantly different now. As the administrator of a G Suite domain, how do you use the Gmail API to programmatically set the email signatures of users in your domain through Google Apps Script? This method uses the Gmail API, the OAuth2 for Apps Script library, and "Domain-wide Delegation of