On my site I am using google play games services to sign in and I want to redirect to an https site but when I am signing in with https set as redirect url and click allow the sign in screen freezes.
Make sure you follow this steps that is stated in the Google Play Games documentation that to modify attributes related to your OAuth 2.0 client ID (web origins and redirect urls for a web app, bundle ID for an iOS app, etc.)
Open the Google Play Developer Console and navigate to your game.
On the Game Details page, scroll to the bottom and click the link to the linked Google Developers Console project.
In the Google Developers Console, select your project.
In the sidebar on the left, select APIs & auth. Make sure that the Google Play Games Services API status is ON in the displayed list of APIs.
In the sidebar on the left, select Registered apps.
Expand the OAuth 2.0 Client ID section and find the attribute to edit.
Also make sure you follow the steps in Creating Client IDs and Configure Service.
Related
I am working on Google Action for smart devices and using Dialogflow interaction schema with Java fulfillment. Fulfillment should call third party API to complete requests. For the purpose of the task, I must use a custom OAuth server. According to docs, I filled Action Account Linking information in Action Console with Grant Type: Authorization Code. For all intents including Welcome "Sign in required" is set.When testing with Google Home device or Google Home surface in Simulator menu, I get clear message "It looks like your Demo Service account is not linked yet. You can link Demo Service to your Google Account from the Google Home app." And as expected I get Linking Card in Google Home App to login and get AccessToken for third party service. Everything is OK here.
But when using Telegram integration or Phone surface in Simulator I just get "It looks like your Demo Service account is not linked yet" and nothing happen neither in Telegram, nor in Google Home App. How should user authentication for third party service be managed in this case?
Using the Actions on Google simulator, when you get the "It looks like your Demo Service account is not linked yet" you can achieve account linking by clicking on the DEBUG tab then open in a browser the url in "debugInfo". (See below)
The Phone surface simulates the Google Assistant app on Android or iOS devices. Users on these platforms will be prompted directly for account linking. (See below image)
I am trying to find the up to date instructions for creating a google android app credentials does not match the google developer console.
https://developers.google.com/youtube/android/player/register
there is no APIs & auth on the sidebar anymore:
In the sidebar on the left, expand APIs & auth. Next, click APIs. In the list of APIs, make sure the status is ON for the YouTube Data API v3.
Please advise.
-Tony
Ok, I figured it out. I was trying to do it from the Google Play Console rather than from the Google Developer Console. But I first needed to tie my Google Play Console to the Google Developer Console using my settings in my Google Play Console.
-Tony
I added clientID and clientSecret (created in Google Developer console) to application.yml but I couldn't get it working. Any idea what is causing error 400. Error: redirect_uri_mismatch. I got http://127.0.0.1:8080 in Authorized JavaScript origins.
I did everything what is said in Google's tutorial, but no luck:
https://developers.google.com/identity/sign-in/web/server-side-flow#step_1_create_a_client_id_and_client_secret
You need to specify in your Google developers console the different redirect url you authorize. For you, you need to add http://127.0.0.1:8080 url.
Little tuto:
Connect to your developer console, click one the main menu
Select API management
Go to Identifiant and select your application, here JHipster
And add your url and save
Another thing that I had to do that wasn't mentioned clearly in the google developer link was to enable the Google+ API.
The various API's are accessible via the Library tab under the Dashboard.
I have implemented the Google maps iframe embed api to my website, the map API is working correctly on desktop web browsers as well as Google Chrome for mobile.
However when i attempt to view the page of my site with the API on in mobile safari on iphone i get an error saying;
"The Google Maps API server rejected your request. This IP, Site or mobile application is not authroised to use this API key".
I Have enabled Google Map API for IOS on the google developer console and the issue still hasnt gone away. As i said the API works fine on other mobile browsers.
Does any one have any suggestions how to fix this?
Thanks, Martin
Did you create a new Client ID?
Handheld devices require "Installed Application" Client ID, not "Web Application. "
In the older apps marketplace, a domain admin could switch off app visibility from the apps admin panel and the authentication/authorization to a 3rd party app still kept working.
After the OAuth2 migration, I see that switching off app visiblity to "Off", stops the 3rd party app to refresh the access tokens (for offline access) and returns access denied. Is this an issue or is it supposed to work this way ? We are using Service account to access.
I do not want the installed 3rd party app icon to appear in Gmail universal navaigation for all the domain users and still the autorization ( and offline acccess) to keep working.
I noticed this change as well. We have had to create multiple marketplace listings to get around this.
1 Listing for users that want the contextual gadget
1 Listing for those users that want the universal navigation
1 Listing for those users that want no universal navigation
You can turn off the universal navigation in the Marketplace Setup console by unchecking "Enable Universal Navigation extension"