So you don’t have to figure it out unless you want to :-). Well, the good news is that it only needs to be solved one time, and we already solved it. The key to this dance is that the web page doing all the dancing has to be hosted on the FileMaker Server. If the server is setup with one or more providers, you’ll get a list of those providers with the URLs they need as part of the process. So nice! After the user logs in, they are redirected back to the original page with tokens of some sort.įileMaker server adds to this dance a little bit by abstracting away the need to know what Providers are configured on the server already. The Provider is responsible for maintaining the username and password, not you. With OAuth, you send the user to a login page that is run and controlled by the “Provider”, and they login on that page with their username and password. We’ll have an article up showing how to do that with Azure. If you can’t connect with FileMaker Pro using OAuth, you won’t be able to use the techniques and sample files from this article. You’ll need to have FileMaker Server setup to use OAuth for client access. In this article, we’ll show how it works and provide some sample code that you can use to get up and running fast. At the time of this writing, there isn’t much in the way of documentation on how to do that. You can log into the FileMaker 16 Data API with OAuth. Authenticating to the FileMaker Data API with OAuth
0 kommentar(er)
