Topics In Demand
Notification
New

No notification found.

Blog
Implementing OAuth in Custom FileMaker Application

April 26, 2018

458

0


Listen to this article



This article is a continuation of the FileMaker OAuth 2.0 Authentication. Here we will show you how OAuth works with some sample code and how it can be used to log on to Custom FileMaker application.

 

Steps Involved-

  • Configure FileMaker Server / Cloud
  • Create Application and configure it on provider’s account
  • Set up Groups or Accounts in FileMaker file
  • Configure FileMaker Server / Cloud

The first step to use OAuth is to enable External Authentication on FileMaker Server/Cloud.

Enabling EA on FileMaker Server: First, you need to login to Admin Console of FileMaker Server and then you can go to Database Server>>Security and in Client Authentication area select FileMaker and External Server Accounts and then enable the OAuth Providers.

Enabling

Enabling EA on FileMaker Cloud: In this case you need to login to Admin Console of FileMaker Cloud and then you can go to Configuration>> Client Authentication, and from there you can enable OAuth Identity Providers.

Enabling

  1. Create Application and configure it on provider’s account

Now that we have enabled OAuth Authentication next we have to Create OAuth Client ID Credentials on provider’s account.

Amazon

Creating

FileMaker

class=image-5

Google

Creating

class=image-7

class=image-8

 

Microsoft Azure

Creating

class=image-10

class=image-11

With Azure, we can also configure to log in with group

  • Create Group in Azure Active Directory
  • Add User to the GroupEnable Group Authentication in Application manifest (set group membership claims: SecurityGroup)


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.