Go to Webservices in your Betty Blocks application and create a new Webservice to request Google's OAuth flow.Ĭlick Save and create a Webservice endpoint.Īlso, create additional Query variables to use in our requests. With the configurations in Google and a data model for storage in place, it's time to create webservices and web pages in our Betty Blocks application that are performing the requests and saving the received values. Now it's time to create a webservice and web page in our Betty Blocks application for this callback to store the access token in! In the background, an access token among other values is generated, which can be used in our further requests. The Google OAuth 2.0 flow should be started correctly, prompting you to log in and after allowing access you should be redirected to the callback URI entered in Google. Google will send this as an additional parameter in the callback so we can recognize the user by this ID.Ĭreate this URI and try to visit it in a web browser. Userid: In this case the record ID of the user we want the access token to be related to.

Redirecturi: The redirect URI should match the Authorized redirect URI you entered when creating a Client ID. A complete list of available scopes can be found here: Google API ScopesĬlientid: The client ID you acquired in the first part. Googlescopes: All the scopes we want the user to have access to.

The URI should be built up as follows: Įach value between the marks are to be replaced with the following values. The next step is to create a URI for users to initiate the actual OAuth user consent flow. In this case, we are going to use the default User model to do this so a User has many GoogleOauthTokens. Var:record.access_token_expires_in != nil & var:record.access_token_issued_at != nil ? var:record.access_token_issued_at + seconds(var:record.access_token_expires_in) : nilĪdd a relation to the user model or any model you want to relate the access token to so you can have a per-user access token in the future. Create a model called GoogleOauthToken and add the following properties:Īccess_token_expires_at: Date time expression Note: Make sure the authorized redirect URI is the URI of the web endpoint you want the OAuth Access token to be posted back to.Ĭlick Create and Google generates a client ID and client secret which we will need in the further process, so copy them so you have them ready! You can always find them again by opening the OAuth 2.0 client IDs in their dashboard.īefore we can continue on to performing requests, we must set up a way to store the acquired access tokens in. Create new credentials and choose OAuth client ID. To do this, go to the Credentials section. The base URL is įirst, you need to create a project in Google APIs and register your Betty Blocks application to enable API services.

In this example, we have a Betty Blocks application with the name Google OAuth Showcase. Obtain an access token from the Google Authorization Server. Obtain OAuth 2.0 credentials from the Google API Console. To get an idea of how Google designed this system, it's best to read up on Google's OAuth 2.0 documentation here: Google OAuth 2.0 and OAuth 2.0 for Mobile & Desktop AppsĪs they explain in the article, using their authentication flow consists of these 4 steps: Whether it's Google Maps, Google Drive, or any of the others, you're all set. This means you only have to implement this integration once in your application and can include it in each workflow you're using Google requests. This access token is a centralized way to authenticate each request.Īll Google requests, no matter which service, work through this system. To determine which Google account you're performing each request with and if you're authorized, you must request an access token. By integrating with them through their REST API you can give your Betty Blocks application a functional boost. Some of those services make a great combination with Betty Blocks.

Google offers all kinds of services, enabling you to get the most out of your business. Note: This article is not fully up to date and isn't using the best practices to develop your application.

Google oauth rest google drive scope