I am trying to add testers for Google Play Services.
However, whenever I use any of my gmail accounts, e.g. fbloggs#googlemail.com / fbloggs#gmail.com, it always returns this message :
The following email addresses could not be added because they are not Google accounts or have not enabled Google+: fbloggs#googlemail.com
I definitely have enabled Google+ because when I go to plus.google.com with this account, I can see Google+ content.
What else do I need to do?
Related
I experience difficulties in login into my google scholar account. It always said ERR_TOO_MANY_REDIRECTS and I can't access my account.
I have tried to access the Google Scholar website using Incognito mode, but still no good. I have also tried to clear all my cookies but still get the same error message.
How to solve this problem?
Thank you.
FYI: I am using Gsuite.
Activate your institution's Google Assistant in G Suite:
Dashboard, Apps -> Additional Google Services -> Google Assistant
If this happens because you used a mail tied to an institution that changed its privacy policy regarding Google and disabled the access to the Google Assistant, there is still a solution: create a new google account, using a new primary email address on which you have the full privileges, but verify your google scholar email with your institution email. This will trigger a duplicate account verification and you will be able to choose what google scholar profile to keep.
So I have implemented Google authentication by using AWS Amplify (federatedSignIn) in my React app. Apparently, I want to make the google account selector screen mandatory for the user to select an account to log in. Apparently, it works only when multiple google accounts are available to choose from, but if there is only one account, the system automatically uses it to login?
How can I enforce the selection screen with only one account?
That is google's functionality. You cannot change how google handles their login requests.
See more: https://developers.google.com/identity/toolkit/web/federated-login
I have a web application setup to handle webhook requests from an Actions-on-Google/Dialogflow application using the Google Assistant. Users don't need to sign-in to a google account in order to use my web application and I'd prefer to keep it that way, so that users can sign in with any email address.
I also want my users to be able to interact with my application using the Google Assistant, and be able to access personal/contextual data via the assistant (i.e. when a speaker says, "what's on my shopping list", the web app needs to be able to know what my means).
Currently, I have this working by using my web app to issue a unique short code to my user (in the web app UI) and then with an intent on the Assistant where the speaker says "My code is 1-2-3-4" and then my web app can identify the user from then on (by saving the userId from the webhook request to whatever user got the short code 1234 and then using that userId to lookup the user on each subsequent request.)
My question is, is there a better way to do this? Ideally, in my web app, I'd like to have something like an "Authorize Google Assistant" button, which would then link the user's google account to their web-app account, so that the conversation on the Assistant is seamless.
Has anyone done this before?
Thanks
This is the perfect use case for Account Linking with the Google Assistant.
From your users' perspective, they will start to use your Action. If they're doing so through a speaker and they haven't linked the account yet, they'll be directed to a mobile device to do so. On a mobile device, they'll be redirected to a page on your website where they will been to authenticate themselves and authorize your server to let them in through the Assistant. Once they have done so, they won't need to log in again, the accounts will be linked, and they'll be able to use the voice Action without further obstruction.
From your perspective as a developer, you'll need to setup an OAuth2 server (I suggest the code flow). That login process I mentioned is the first step in the OAuth dance, and will end up with you issuing a code to Google. They will then exchange this code for an Auth Token (with a limited lifetime) and a Refresh Token (which does not expire). They will periodically use the Refresh Token to get new, valid, Auth Tokens for this user. When the user issues a voice command, the Auth Token will be passed as a field in the JSON to your fulfillment server, and you can use this to verify who the user is and that they are authorized to use your service.
I want to use Google as OAuth provider for my web site. So I created a new project in Google Developers Console. There under "Consent screen" I wanted to set the email address my users can see when logging in to my company's non-Gmail address.
However, since this is a drop-down box I can only choose from one of the associated accounts, set in the project's permissions. My problem is that I need to set an email address that does not belong to Google, nor do I have a Google Apps account.
So my question is: Can I set a non-Gmail email address in a Google project, even if that domain is not in Google Apps?
You will have to register an account at google developer with your non-gmail address first. And then go to Permissions in the Google Developers Console, add a Member with the non-gmail account as owner. After that you will be able to select the non-gmail email address in Consent screen.
I can't see any way to delete apps from the G+ Manage Apps page. I can disconnect there, or revoke access from the Google OAuth authorized apps page, but I can't see any option to remove it altogether.
Disconnecting using the Google+ Apps page will let you remove all the activities associated with the app, and will revoke access to your information to the app in question. It should also delete it from the list.
Update
For the record, this link currently redirects to https://myaccount.google.com/permissions which does the same thing.