How to enable Frontify Content Connector

Updated December 09, 2024 19:24

This article guides you through the setup of Frontify integration.

Prerequisites

Admin/owner access to the Templafy tenant.
Content Connectors modules enabled.
Frontify Enterprise Plan
Frontify service account & API key for authenticating the integration if using Service Account Authorization in Templafy (organization content / same content for all users)
An OAuth2 Client must be created in Frontify if using OAuth 2 Authorization Code with PKCE in Templafy (user specific content)
- The redirect URL should be set to https://public.templafy.com/integrations/oauth/login-callback
- "Confidential" configuration option should be set to Off

How to configure Frontify

Go to Integrations section.
Go to Available tab.
Search for Frontify.
Click +.
Fill out required fields:
- Base URL - Url: <Frontify domain of client>
  e.g. brandname.customername.com
- Library Type - possible options are Image, Icon, or Logo
Select desired Authentication Type:
- Service Account Authorization will display the same content to all users without login (organization's content).
- OAuth 2 Authorization Code with PKCE will require user login and will display user specific content.
Based on the selected Authentication type, fill out the necessary configuration field:
- For Service Account Authorization:
  - Token: Service User token generated in Frontify.
- For OAuth 2 Authorization Code with PKCE:
  - Client ID: Client ID from the OAuth2 Client created in Frontify.
Hit Save.

OAuth 2 Authorization Code with PKCE

Service Account Authorization

When connecting to Frontify via OAuth 2 Authorization Code with PKCE, users will need to consent to Templafy accessing libraries / projects. This will need to be approved when the access token expires or is invalidated (user logs out).

Important

The Frontify content connector can have only one authentication type at a time; if several authentication types are required, several connectors should be set up.

Note

If the Frontify Content Connector is utilizing OAuth 2 Authorization Code with PKCE as an authentication type, the following should be noted:

When not logged in, the user will not be able to access any Frontify content; the content will only be displayed once the login has been successful.
When logging in, requested scopes will be displayed to the user, and they must be approved (More information on scopes can be found here). In this case, Templafy requests Read access to libraries / projects.
If the user is already logged in on the Frontify side, the log in on Templafy's side will be seamless as the token already exists.
If the user isn't already logged in on the Frontify side, the user will need to provide Frontify credentials to log in as the token cannot be found.
If a user has multiple Frontify accounts and needs to switch between these accounts, this can be performed by logging out and logging in again within the same browser, OR by opening a different browser (or incognito) and logging in with the desired account.

Related to

frontify connector dam

Articles in this section