Page Contents

    Securing Experiences Using Auth0

    In this topic you will learn how to secure experiences using Auth0 SSO.

    When an experience is secured using SSO, users will be required to authenticate before they can access a Web or Mobile App Experience.

    The steps in this topic assumed you have created a Auth0 trial account and have confirmed your account through email.

    Creating an Access Control Profile

    You need to create an Access Control Profile that will be used to secure any experiences you want to secure using SSO.

    1. Log in to your Brightcove Engage account.
    2. Click Settings in the header.
    3. In the left navigation click Access Control Profiles.
    4. Click Create Profile.
    5. Give the profile a Name.
    6. Check the SSO option.

    To complete the Access Control Profile, you need some values that will be provided as part of the Auth0 application creation process. After creating a new Auth0 application, we can finish creating this profile.

    Creating an Application

    Next, you need to create an application that will be secured using Auth0. As part of the application creation process, the signing certificate and SAML protocol URL will be used by the Access Control Profile created in the previous section.

    1. Log in to your Auth0 account.
    2. On the Getting Started page, in the left navigation, click Applications.
    3. On the Applications page, click + CREATE APPLICATION.
    4. Enter a Name for the application.
    5. Select an application type of Regular Web Applications.
    6. Click CREATE.
    7. Click the Settings link below the application name.
    8. (Optional) Locate the Application Logo field and enter a URL to your application logo. This will cause your logo to appear on the login page vs. the Auth0 logo.
    9. Confirm that the Token Endpoint Authentication Method is set to POST.
    10. In the Allow Callback URLs field, add the following URL:
    11. At the bottom of the page, click the Show Advanced Settings link.
    12. Click the Certificates link.
    13. Copy the Signing Certificate to the clipboard.
    14. Return to Brightcove Engage and the Access Control Profile you created in the prior section.
    15. Paste the Signing Certificate into the X.509 Certificate field.
    16. Remove the ---BEGIN CERTIFICATE--- and ---END CERTIFICATE--- lines from the X.509 Certificate field.
    17. Return to Auth0.
    18. Click the Endpoints link.
    19. Locate the SAML Protocol URL and copy it to the clipboard.
    20. Return to Brightcove Engage and the Access Control Profile you created in the prior section.
    21. Paste the SAML Protocol URL into the SAML 2.0 Endpoint (HTTP) field.
    22. Check the Expose all attributes option at the bottom of the page.
    23. Click Save to save the Access Control Profile.
    24. Return to Auth0.
    25. At the top of the page below the application name, click the Addons link.
    26. Enable the SAML2 WEB APP option.
    27. In the Application Callback URL field, add the following URL:
    28. Scroll to the bottom of the dialog and click ENABLE.
    29. Close the dialog.

    Make sure you save the changes to the application settings.

    Creating a User in Auth0

    This topic uses a trial account of Auth0. By default, no users are created. You may need to add a user to complete the testing process.

    1. Return to Auth0.
    2. In the left navigation, click Users & Roles > Users.
    3. Click + CREATE USER.
    4. Enter the user info and click CREATE.


    Assign the Access Control Profile to an experience

    The last step is to assign the Access Control Profile that was created to the experience(s) you want to secure.

    1. Return to Brightcove Engage.
    2. Edit the experience you want to secure.
    3. In the left navigation, click SITE CONFIGURATION > Access Control.
    4. Select the Access Control Profile that is associated with the Auth0 SSO configuration.
    5. Click Save.
    6. Publish the experience.

    When you access the experience, you should be prompted by Auth0 to login. The following image is when trying to access a Mobile App Experience.

    Page last updated on 19 Jun 2021