I use google authenticator to log in to websites with 2fa i have to go to mobile app whenever I want to see the 2fa code, I want to get it directly from my computer. Is it possible somehow?
What i want is that i can access authenticator from my computer and mobile at the same time.
So I Googled that for you:
https://www.google.nl/search?client=ms-android-google&ei=q9TZWYbaFdGiwAKjjZtA&q=google+authenticator+for+windows&oq=&gs_l=mobile-gws-serp.1.1.41l3.0.0.0.3454.1.1.0.1.1.0.0.0..1.0....0...1..64.mobile-gws-serp..0.1.12.3...110.anFAezNz27s
And this article (first Google result) https://www.google.nl/amp/s/www.maketecheasier.com/google-authenticator-windows/amp/ describes that it is written on an open standard and that there are Windows programs like WinAuth, you can download to use Google Authenticator.
Related
I have created a project at Google Developer Console. And I have followed the steps to create an OAuth Consent screen to ask users for their consent to let me use their email address and Google Calendar for my App. App is still at Test Mode, and everything is working fine.
But for the users of Google Workspace (G Suite) (#domain.com) the consent screen is not working. It just ends up saying that Something went wrong and ... the request is malformed.... I am sure it isn't malformed, because it is just working fine for non-workspace (#gmail.com) users.
I got it working later by Manage Domain Wide Delegation by logging into the Google Workspace Admin account and manually setting up my Apps's service account Client ID and Scopes. The process allowed users of that #domain.com (non-admin) email to get my consent screen working.
But this is not practical. I can't ask every #domain.com email address user to contact their Google Workspace Admins and add my app to the domain wide delegation area manually.
There are apps and services out there which connected to my non-admin Google Workspace account without having my Admin do it for me.
So there must be some way to get my consent screen work on #domain.com email addresses hosted at Google Workspace without involving the Admin account or Domain wide delegation stuff.
How can I get it done? Please help, I can't find any solution online.
EDIT More banging head in the wall, but no similar issues found on the internet. So what I feel like is that I need to wait for my OAuth application to be approved for production for it to work for Google Workspace accounts. PLEASE HELP if you know there is some other issue and I can try to fix...
Thanks.
Looks like there was some temporary issue with Google. I emailed them, and the issue was fixed.
I created an App with the GSuite administrator account. But now when I go back I am my work user(rob) and have no access to the App I created.
If I then go to Google and switch accounts there is no issue for all other Google apps(drive, gmail etc) but Appmaker still shows me as rob.
How can I convince App Maker to work like all other Google apps and let me select the logged in user?
Most likely it happens because at this time App Maker doesn't provide users with account chooser widget like most other Google products. Here are some things to try to bypass this limitation:
use different chrome instances for better accounts separation (https://support.google.com/chrome/answer/2364824) - I would highly recommend this approach. I have about 10 different accounts and this feature saves me tons of time and gives peace of mind
use incognito window
log out from other accounts (in theory, when you open AM it will ask you to choose an account and re-login)
I am a web developer, and offer the creation of Google Analytics accounts for clients. To save them messing around with veifying email accounts, I like to create them a gmail account, get it all set up then just send them the password.
However, Google is asking for verification by Mobile and I have now reached the "verification limit".
I kind of understand why Google don't want spam accounts, but is there no way to regsiter as a developer and then create accounts for clients? Something like apps for business, but just for standard Google accounts.
Thanks #CrayonViolent it looks like profiles is the way forward
I would be a mistake to use profiles for multiple clients. For one, each client would be prevented from using more than one profile. And there is a limit of 50 profiles per account.
How does the Google single sign on works (OR any website's SSO)?
For example, once I login to the Gmail, it lets me see "My places" on Google Maps without signing in again? Same with Yahoo mail and Yahoo notepad.
I am guessing this checking is done locally within the browser. But any more details would be appreciated.
It is done with a cookie, that is accessible to all sub-sites on google, and it contains identification numbers. Then the sub-site queries the account server, gives the cookie, and the account server will return the user.
Actual implementation details may vary (as I am not a Google engineer), but I think you want to know how to do it, not what google does.
Is it possible to access a mobile users phone contacts from a web page? The company I work for would like to use QR codes to direct people to a coupon on their website and then give viewers the option of sending the url to their friends in a text message.
Obviously this would be an opt in service. Perhaps you would need to build a mobile application to accomplish the task? If anyone has an idea on how to accomplish this or something similar please let me know.
As far as I know, it is not possible to access the contact database via a web page, on any of the major platforms; in order to access this data, a native application is required.
Nate is right.
The only thing that you can do (that won't accomplish everything you need) is encode SMS message in QR code (e.g. "sms:number:subject" see http://code.google.com/p/zxing/wiki/BarcodeContents), this way your company will get user's phone number as part of SMS message, but not numbers of his/her friends.
An API for accessing contacts is being built into the WebApi by Mozilla but as of today it's not enabled by default and I expect cross browser support is still far off.