Google states:
You must provide a developer email when you create your developer
account; here are some tips about which email to use:
Because you will receive important emails about your extension or you
may want to delete one of your accounts, we suggest using a new email
account just for publishing your Chrome Web Store items.
https://developer.chrome.com/docs/webstore/register/
What does "wanting to delete one of your accounts" mean? Is this specific for the developer account or do they refer to the Google account?
Here they state:
First you will need to register as a Chrome Web Store developer. We
suggest using a new account just for your item instead of your
personal account.
https://developer.chrome.com/docs/webstore/publish/
What does a "new account just for your item mean"? Does this mean a separate account for each extension I publish? Again, what type of account? Can a Google account hold multiple developer accounts so the reference is to the developer account or do they mean separate Google accounts per item?
Related
I'm trying to get the Google Client Id (found under https://plus.google.com/me) of a user corresponding to the account he's currently connected with.
Explanation: when connecting with your gmail account on Chrome, the result of the code given here (https://developers.google.com/+/web/people/) gives the user's client ID that I need to use the Google Payment API.
The problem is if the user has multiple accounts connected on Chrome.
Example: Our user has an email account for work (WEmail) and a personal email account (PEmail). He first connects to chrome using his WEmail. Then adds his PEmail to the list of Chrome connected accounts. Then our user wishes to make a payment on an extension he has installed, with his PEmail.
The issue here is that to process such a payment you need the google client ID of that user, and when you fetch it, you will get the one of the first connected account (WEmail) and not the one of the current used account (PEmail). Which makes it impossible to process the payment since you might not be serving the right account.
Is there any way to get all the currently used ids of a user or jsut the currently used id?
If not, are there plans to integrate such a solution in the short term?
Thanks for your help.
For users that are logged into multiple accounts, how can a script let the user pick an account? For example, Gmail, Google Drive, etc. provide a way for the user to select which account to use with a selectable option on the top-right of the page:
How can developers implement a similar mechanism?
There seems to be no way to do that with Google Apps Script libraries - GAS just uses the current primary account. Also, unfortunately, the API Client Library and thus Google Sign-In for websites don't work inside GAS web apps because of the sandbox frame. You could write your own or use some existing OAuth implementation to authenticate with Google but I found a much much simpler solution using Auth0 Lock with only a Google Connection (using the popup method because the redirect method doesn't work within the sandbox frame).
With Chrome Version 70.0.3538.102. You may resolve your issue (at least i did)
Now i make sure i ONLY signed in ONE account at a time. Then use "manage people"
if i have 3 google accounts, i will create 3 people and each time you only have 1 active google account session. With this setup, i ensured everytime my script only execute with my G Suite user instead of #gmail accounts
You can try using the Directory API to work with Apps Script. Retrieve the user using:
GET https://www.googleapis.com/admin/directory/v1/users/userKey.
You can then make an interface that displays the user accounts details(Name, email,etc).
I would like to use Google Forms as a means for the users of my system to enter their login credentials to various system tools.
The reason this is important is because as their admin, I will need to manage various aspects of their tools.
Users are (rightly so) anxious of entering passwords in clear text boxes. What is the best method for retrieving such information in a safe and user-friendly manner?
You should NEVER collect user credentials for 3rd party services, e.g. collecting username/password to Google accounts. Not even if this is a Google Apps account belonging to your organisation (note that google gives admins the ability to reset password but not to view it). Also, a lot of users are now using two-step verification, so collecting user credentials will not work.
If you need to access Google services in the name of the user, than you should look into OAuth.
We are working on testing email on-premise and may be considering moving away from Google Apps for Email. Our current projects within GCE are tied to our current Google Apps Email accounts. Do we have to use Google Apps Email in order to use GCE? If not, does anyone know how login to the GCE web console would work since it is currently tied to our Google Apps Email accounts?
I can't seem to find a proper way to shift the project to a non-google authentication method.
You do need a Google account to use Google Cloud Platform services. However, it doesn't need to be a Google Apps account, you can use a free Gmail account as well.
I believe you need a google "apps" account for everything since you will have to pay for your GCE and payment comes from a profile that is associated with that account.
If you move your email, assuming your domain is using Google's services now, I think you Google account will still use that domain's email login for the Google account even if you change your MX records to use a different email host.
Or maybe I don't understand your question ...
I'm using Google Apps Script UI to create forms for students at my school. I've restricted access to my domain for added security, and to capture users' email addresses.
The problem is that many of our students have separate Gmail accounts. If they are already logged into Gmail (not our domain), they don't get a log-in page, but something prompting them to request access.
Any suggestions for avoiding this?
Thought I saw a request in the issue tracker for an account choosing feature, but my guess is that you'll want to allow anyone to access your web app and show a custom prompt if their email is non-domain. I don't know how well this would work with shared computers, but creating separate Chrome user accounts for each of my Google accounts has solved all my multiple sign-in pain.