curl is required to use the filemaker api.

The abstract OAuth 2.0 flow illustrated in Figure 1 describes the The original specification ( IETF RFC 6749), which actually is a pretty good read, describes the following basic protocol workflow: Authentication/Authorization server: The server that manages authentication and authorization of the Resource Owner.If you are developing a PHP application for example hat need to connect to a FileMaker Server with the end user authenticating with its Google account, then your application is called the Client. Client: An application making protected resource requests on behalf of the Resource Owner and with its authorization.Resources can be personal data on a Facebook server, and in our context are data that live in a FileMaker database on a FileMaker Server Resource Server: The server hosting the protected resources.Resource Owner: This is the end user that want to.In order to fully understand what is going on, you need to be familiar with some OAuth 2.0 concept. End users can have their credentials safely in one place, and log in through OAuth in a multitude of apps. OAuth 2.0 eliminates this need, and literally gives the key to the end user, so she or he can decide wether your application is authorized to access some FileMaker data, and let an external authentication provider like Amazon, Google or Microsoft security handle authentication.

This is obviously a serious security risk. Before FileMaker Server 16 for example, if you wanted to get data from a FileMaker database with the CWP, you needed to store an accountname and password in some place, like a file or an external database. Now, why bother with OAuth at all? If this really is the new kid on the block, what benefits does it have? There are a few advantages of using OAuth over other authentication and authorization methods, the main one of which is that a client application does not need to store credentials to log in into a FileMaker database. No other knowledge is required. Although referring to PHP at some points, the outline is quite generic and can be used to in any other programming languages capable of making HTTP calls. you know what an HTTP method or an HTTP header is. This blog article assumes you have some basic knowledge of the HTTP protocol, i.e.

With this connector, any PHP application only needs to instantiate a class object and do a few things to connect to the FileMaker Data API. I developed a PHP connector for the FileMaker Data API which is freely available on Github. In this blog article, we will walk through all steps involved to connect a web application to the FileMaker Data API using OAuth. Trying to make this work with a PHP client application, I found out that there are some caveats. The steps involved are described in the FileMaker Data API Guide. You can connect to the FileMaker Data API using OAuth 2.0.

Curl is required to use the filemaker api.