Bynder

Squiz has built an integration with Bynder using existing Squiz DXP features.

This integration enables users to use imagery managed in external digital asset managers within their page content.

Users can configure the integration to use Bynder with their DXP components.

The integration works with squizimage integration.

Anywhere an image is used in a formatted text or as an image included in a component, you can select an image from Bynder as a source.

Configuration

To use Bynder as a Digital Asset Management (DAM) option, Bynder must be integrated through the DXP configuration settings page.

This procedure assumes you have the Admin, Developer, or Owner role required to undertake this task.

All steps and fields in this procedure are required except where noted.
  1. Navigate to Configuration  DAM integrations

    configuration dam integrations
    Figure 1. Configuration page with DAM integrations highlighted.
  2. Click the add_circle_outline Add DAM button.

    configuration dam integrations add dam
    Figure 2. DAM integrations page with ⊕ Add DAM button highlighted.

    The ⊕ Add DAM dialog presents.

    configuration dam integrations add dam modal
    Figure 3. ⊕ Add DAM dialog.
  3. Provide a Friendly name for the integration.

    Choose a name that is descriptive and memorable. Generic names are challenging to manage in greater numbers.

  4. Select Bynder from the Integration type drop-down.

  5. Click the green Add button.

Details
  1. Supply a Friendly name.

    This field automatically takes the value provided previously in the ⊕ Add DAM dialog.

  2. Select Bynder from the drop-down list in the Integration type field.

    integration name details box
    Figure 4. Add DAM details.
Render settings
  1. Provide the sign-in details for your Bynder instance:

    • Enter Auth URL.

      This URL is used to redirect the user to the authorization application endpoint in the front-end authorization flow.

      The format is as follows: https://{bynder-url}/v6/authentication/oauth2/auth.

      Replace {bynder-url} with the root domain from step 9.

    • Enter Client ID.

      This is the Client ID for the front-end application authorization flow.

    • Enter Client Secret.

      This is the secret for the front-end application authorization flow.

integration name render settings
Figure 5. Render settings dialog.
Configuration settings
  1. Supply the root domain for your Bynder instance in the DAM domain field.

  2. Add (or confirm) the Scopes available to the integration.

  3. Provide the Access token URL.

    This is the URL to the token endpoint to retrieve an access token which can be used to authorize API requests in machine to machine flow.

    The format is as follows: https://{bynder-url}/v6/authentication/oauth2/token.

    Replace {bynder-url} with the root domain from step 9.

  4. Enter the Machine to machine client ID.

    This is the Client ID for the machine to machine application authorization flow.

  5. Provide the Machine to machine client secret.

    This is the secret for the machine to machine application authorization flow.

integration name configuration settngs
Figure 6. Configuration settings.
Enable integration
  1. Toggle this switch to enable the integration.

integration name enable integration
Figure 7. Enable integrations toggle.
Authorization redirect URI
  1. Supply an Authorization redirect URI

    integration name auth redirect
    Figure 8. Authorization redirect URI.

Setting Up Bynder Integration

This section explains how to create your own integration in Bynder and obtain the necessary credentials.

Creating OAuth Applications in Bynder

  1. Log in to your Bynder instance.

  2. Click on the cog icon in the top right corner and select Advanced settings  Portal settings.

    bynder oath
    Figure 9. Advanced settings → Portal settings.
  3. From the left-side menu, click on OAuth Apps.

  4. Click the Add new app button.

    bynder oath add app
    Figure 10. Add new app button.

Creating the two required authorization applications

Two applications have to be created:

Creating Front-End Authorization Application

  1. Click the Add new app button.

    The Add new app form presents.

  2. Fill in the form:

    Application name

    Front-End Authorization Application.

    Homepage URL

    (Leave empty)

    Application description

    This is to allow access for frontend applications.

    Integration

    Select other.

    Integration name

    Client authorization flow.

    Select grant type

    Authorization Code + Refresh Token.

    Authorization Redirect URIs

    Copy the URI from Step 15: Authorization Redirect URI and replace MATRIX with the actual CMS domain.

    Set HTTP access control (CORS)

    Leave blank.

    Select scopes

    Select the following scopes:

    • asset:read

    • asset:write

    • asset.usage:read

    • asset.usage:write

    • collection:read

    • collection:write

  3. Click the Register Application button.

  4. Copy the Client ID.

    Paste this value into the Client ID field of Render settings.

  5. Copy the Client Secret.

    Paste this value into the Client Secret field of Render settings.

Creating Machine to Machine Authorization Application

  1. Click the Add new app button.

    The Add new app form presents.

  2. Fill in the form:

    Name

    Machine to Machine Authorization

    Home Page URL

    (Leave empty)

    Description

    This is to allow access for backed applications.

    Integration

    Select other.

    Integration Name

    Machine authorization flow.

    Select grant type

    Client Credentials.

    Assigned User

    From the dropdown, select the user who will authenticate on behalf of the system.

    Set HTTP access control (CORS)

    Leave blank.

    Select scopes

    Select the following scopes:

    • asset:read

    • asset:write

    • asset.usage:read

    • asset.usage:write

    • collection:read

    • collection:write

  3. Click the Register Application button.

  4. Copy the Client ID.

    Paste this value into the Client ID field of Render settings.

  5. Copy the Client Secret.

    Paste this value into the Client Secret field of Render settings.

API rate limits

The Bynder API enforces a rate limit of 4500 requests from a single IP address in any five-minute time frame.

Read the Bynder documentation for more information.

  • Tags are applied to assets through Bynder and sourced by the integration.

  • Tags appear in a list on the left of the file browser.

  • Users can select one or more tags to filter the images presented.