Supporting OAuth without whitelisting connect.adeptia.com

In the event of Adeptia Connect users not willing to whitelist theconnect.adeptia.com server to exchange data with the REST based business apps (endpoints) supported in application, they need to do the followings.

• Register the app on the business application developer portal
• Make configurational changes in Adeptia Connect

1. Register the app on the business application developer portal

   1. Create an app (API) on the developer portal of business application. For example, in case of Dropbox, create an app in the developer options.

      	Once app is created, you get the following details about the app: AppKey and App KeySecret.

   2. Configure the Redirect URL which contains the IP of locally accessible environment. For example, in case of Dropbox, it will be https://<IP>/rest/applications/<Application internal name>/accountURL. Refer to the table below to get the Application internal namefor each business app.

      Application display name	Application internal name
      BigCommerce	bigcommerce
      Facebook	facebook
      FreshBooks	freshbooks
      Azure Blob	microsoftazure
      HubSpot	hubspot
      Magento	magento
      QuickBooks	quickbooks
      Xero	xero
      SageOne	sageone
      Shopify	shopify
      Concur	concur
      Salesforce	salesforcerest
      Box	box
      Dropbox	dropbox
      Google Drive	googledrive
      Zendesk	zendesk
      Zoho CRM	zohocrm
      Google Spreadsheets	googlespreadsheetsrest
      Microsoft SharePoint	microsoftsharepoint
      ServiceNow	servicenow

2. Make configurational changes in Adeptia Connect

3. Configure the parameters in adapter.propertiesfile as instructed below:

   1. Go to …< ConnectServerInstallFolder> \AdeptiaServer\ServerKernel\etc ****location.

   2. Open adapter.properties file.

   3. SetApp key: (Key generated in business application developer app)

   4. SetApp secret: (Secret generated in business application developer app)

   5. Set the value for enableProduction property to False to enable the use of Client ID (App Key) and Client Secret (App Key Secret) for authentication purposes. For more information, refer to "Setting the enableProductionproperty".

   6. Save the file.

   7. Restart Connect Server.

   8. Configure the parameters in apps.propertiesfile as instructed below:

      1. Go to …< ConnectPortalInstallFolder> \resources_config ****location.
      2. Open apps.properties file.
      3. SetApp key: (Key generated in business application developer app)
      4. SetApp secret: (Secret generated in business application developer app)
      5. Set the value for enableProduction property to Falseto enable the use of Client ID (App Key) and Client Secret (App Key Secret) for authentication purposes. For more information, refer to the "Setting the enableProduction property" section.
      6. Save the file.
      7. Restart Connect Portal.

Setting the enableProduction property

• Setting the value for enableProductionproperty in adapter.properties file
  1. Go to …< ConnectServerInstallFolder> \AdeptiaServer\ServerKernel\etc ****location.
  2. Open adapter.properties file.
  3. Set the value of enableProduction property to True or False.
  4. Save the file.
  5. Restart Connect Server.
• Setting the value for enableProductionproperty in apps.properties file
  1. Go to …< ConnectPortalInstallFolder> \resources_config ****location.
  2. Open apps.properties file.
  3. Set the value of enableProduction property to True or False.
  4. Save the file.
  5. Restart Connect Portal.

	If you want to authenticate to a business app using connect.adeptia.com, do the followings: • Set the enableProduction property to true. • Ensure that the client machine you are using is in public domain. • Whitelist connect.adeptia.com with your organisation's firewall.

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs