In order to connect Bynder to Creative Force for certain functions, you will need to create your OAuth Apps in Bynder. In this article, we will walk through the steps required so you can move forward in adding Bynder as an Asset Delivery Location.
🗣️ Tip: Depending on your permissions and familiarity with the technology/interface, you may need to request assistance from your internal IT Team, or Bynder account contact.
Workspace ID & Secret
In Bynder, we will need to generate a Workspace ID and Bynder Workspace Secret, allowing us to connect with the Bynder API to deliver assets to you.
Bynder has this very helpful article on how to generate your Workspace ID and Secret. You will need to have a separate Workspace ID and Secret for each of your CF Workspaces.
Create OAuth Apps in Bynder
For the Authorization redirect URIs you can use the following:
For the HTTP access control (CORS), you can use the following:
Select grant type: Client Credentials
Assigned user: ensure that the account has the correct permission set in Bynder.
Set Scopes
Make sure you select the following scopes:
asset: read
asset: write
⚠️ Important: Bynder does not allow users to update the OAuth scope; you need to ensure that all of the "Assets" and "Metaproperties" scopes are selected when creating the OAuth app.
Otherwise, you will need to create a new OAuth app so that Creative Force can connect with Bynder as expected.