This PHP class can be used to interact with the Google Authenticator mobile app for 2-factor-authentication. This classcan generate secrets, generate codes, validate codes and present a QR-Code for scanning the secret. It implements TOTPaccording to RFC6238
For a secure installation you have to make sure that used codes cannot be reused (replay-attack). You also need tolimit the number of verifications, to fight against brute-force attacks. For example you could limit the amount ofverifications to 10 tries within 10 minutes for one IP address (or IPv6 block). It depends on your environment.
Visit the page on your desktop and type the name, user and secret key, then point your mobile device at your monitor to scan the code into Google Authenticator (or whatever app you’re using to generate the six-digit codes). Google Authenticator generates 2-Step Verification codes on your phone. 2-Step Verification provides stronger security for your Google account by requiring a second step of verification when you sign in. Google Authenticator can issue codes for multiple accounts from the same mobile device. Each Google Account needs a different secret key. To set up additional accounts, turn on 2-Step Verification for each account and use the same Google Authenticator app.
Usage:
See following example:
Running the script provides the following output:
Installation:
composer install
Run Tests:
ToDo:
![]() Notes:
If you like this script or have some features to add: contact me, visit my blog, fork this project, send pull requests, you know how it works.
This guide describes how an application authorizes requests to the Management API.
Authorizing Requests
Before users can view their account information on the Google Analytics web site, they must first log in to their Google Accounts. Similarly, when users first access your application, they need to authorize your application to access their data.
Every request your application sends to the Analytics API must include an authorization token. The token also identifies your application to Google.
About authorization protocols
Your application must use OAuth 2.0 to authorize requests. No other authorization protocols are supported. If your application uses Google Sign-In, some aspects of authorization are handled for you.
Authorizing requests with OAuth 2.0
All requests to the Analytics API must be authorized by an authenticated user.
Google Authenticator Private Key View Generated
The details of the authorization process, or 'flow,' for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:
Some flows include additional steps, such as using refresh tokens to acquire new access tokens. For detailed information about flows for various types of applications, see Google's OAuth 2.0 documentation.
Google Authenticator Private Key View Generate Account
Here's the OAuth 2.0 scope information for the Analytics API:
To request access using OAuth 2.0, your application needs the scope information, as well asinformation that Google supplies when you register your application (such as the client ID and theclient secret).
Tip: The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the page with libraries and samples for more details.
Common OAuth 2.0 Flows
The following lists common use cases for specific OAuth 2.0 flows:
Web Server
This flow is good for automated, offline, or scheduled access of a user's Google Analytics data.
Example:
Client-side
This flow is ideal for applications when users interact directly with the application to access their Google Analytics data within a browser. It eliminates the need for server-side capabilities, but it makes automated, offline, or scheduled reporting impractical.
Google Authenticator Key
Example:
Installed Applications
This flow is for applications that are distributed as a package and installed by the user. This flow requires that the application or user have access to a browser to complete the authentication flow.
Examples:
Google Authenticator App KeyService Accounts
Service accounts are useful for automated, offline, or scheduled access to Google Analytics data for your own account. For example, to build a live dashboard of your own Google Analytics data and share it with other users.
To get started using Analytics API, you need to firstusethe setup tool, which guides you through creating a project in theGoogle API Console, enabling the API, and creating credentials.
So these functions, essentially, are functions that map, that outputs, positive real values. But they're functions that act on non negative integers, okay? Types of stream ciphers. So, are non negative real values that are supposedly probabilities.
To set up a new service account, do the following:
Your new public/private key pair is generated and downloaded to your machine;it serves as the only copy of this key. You are responsible for storing itsecurely.
Note: You need to add the service account email address as an authorized user of the view (profile) you want to access.
Troubleshooting
Your authorization fails in these situations:
Sep 07, 2018 Key Quests were separated into their own specific group upon quest selection, making progression through the game almost trivial. Monster Hunter Generations Ultimate, on the other hand, fits squarely in line with previous Monster Hunters.
OAuth 2.0 playground
This tool allows you to go through the entire authorization flow through a web interface. The tool also displays all the HTTP request headers required for making an authorized query. If you can't get authorization to work in your own application, you should try to get it working through the OAuth 2.0 playground. Then you can compare the HTTP headers and request from the playground to what your application is sending to Google Analytics. This check is a simple way to ensure you format your requests properly.
Invalid grant
When you try to use a refresh token, the following returns you an
invalid_grant error:
Applications can request multiple refresh tokens to access a single Google Analytics account.
Google Authenticator Key Code
For example, if a user wants to install an application on multiple machines and access the same Google Analytics account, then a separate token would be required for each machine. When the number of refresh tokens exceeds the limit, older tokens become invalid. If the application attempts to use an invalidated refresh token, an
invalid_grant error response is returned.
The limit for each unique pair of OAuth 2.0 client and Google Analytics account is 25 refresh tokens. If the application continues to request refresh tokens for the same Client/Account pair, once the 26th token is issued, the 1st refresh token that was previously issued will become invalid. The 27th requested refresh token would invalidate the 2nd previously issued token and so on.
Note: The limit of 25 refresh tokens is subject to change.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |