In fmOAuth (0.0.2), OAuth authentication (Google) implements a function that can use arbitrary applications

Hello.
I am Teruhiro Komaki of frudens Inc.

Although it may be a bit hard to understand from the title, it is implemented so that you can replace the consent screen with any application, not fmOAuth(default).

That way, you can login to the console with your Google account, have the application created, and pass the arguments.

How to write your own app, write another article.

Consent screen of fmOAuth

The default agreement screen is as follows.

fmoauth-002-google-oauth-application1

Consent screen of arbitrary application

When creating an application on the console (GCP) and passing the information of the application as a script argument, the following agreement screen will be displayed.

fmoauth-002-google-oauth-application2

Continue reading →

1 Comment

developing Gmail API (download and send) to fmOAuth (0.0.2)

Hello.
I am Teruhiro Komaki of frudens Inc.

It is a blog after a long absence.

We released a beta version (0.0.1) of the solution fmOAuth at the end of last year (2017).

After releasing it, I could not develop for a while, but I have been working on development continuously as I got a little time.

We added a script to access Gmail API in this release (0.0.2).

As a result, you can download Gmail and you can send mail via API.

As for sending e-mail, I thought that it was unnecessary because I can send e-mail at the script step of the FileMaker, but I implemented it because it’s peculiar.

By the way, now it will be plain text transmission.

Gmail API

fmoauth-002-gmail-api-download-send1

Gmail API Response data

fmoauth-002-gmail-api-download-send2

Continue reading →