support Contact Support | system status System Status

Configuring Single Sign-On with Active Directory Federation Services

In this topic you will learn how to configure Brightcove Engage™ to support single sign-on using Active Directory Federation Services (ADFS).

Before you get started

Complete these initial setup steps:

  1. Enable RelayState for iDP-initiated sign on by following the instructions here. The location varies depending on the version of ADFS that is being using.
  2. Restart the ADFS service so the changes are applied.

Adding an Access Control Profile

  1. Open Administrative Tools from the Windows Start menu or Control Panel and then open the AD FS Management application.
  2. Open Service > Certificates in the left hand explorer panel.
  3. Double-click on the Token-signing certificate that you want to use.
  4. Click on the Details tab and click Copy to File…
  5. Click Next in the export wizard, then select the Base-64 encoded X.509 (.CER) option.
  6. Save the certificate file to your local file system. Open the certificate in a text editor. This is the certificate that will be used to setup the Access Control Profile in Brightcove Engage.
  7. Open Brightcove Engage.
  8. Click Projects > Settings.
  9. Click Access Control Profiles in the left navigation.
  10. Click Create Profile.
  11. Give it a Name and then select SSO - Requires a username and password for access.
  12. In the SAML 2.0 Endpoint (HTTP) field, enter the URL to the iDP-initiated sign-on page for your ADFS server. This usually ends in IdpInitiatedSignOn.aspx. For example, if the SP-initiated sign-on link is https://sso-test.brightcove.com/adfs/ls, the iDP-initiated sign-on page is https://sso-test.brightcove.com/adfs/ls/IdpInitiatedSignOn.aspx.
  13. Check the My SSO System is ADFS (Active Directory Federation Services) option.
  14. Copy and paste the certificate that you saved in step 6 into the X.509 Certificate field.
  15. Click Save to save the access control profile. The new access control profile should appear in the list of profiles.
  16. Back in the AD FS Management application, open Relying Party Trusts.
  17. Click Add Relying Party Trust… in the right hand panel.
  18. Click Start in the wizard and then paste the Metadata URL that was displayed in step 15 into the Federation metadata address field.
  19. Click Next and then give your relying party trust a name.
  20. Continue clicking Next until the Finish step. Uncheck the Configure claims issuance policy for this application checkbox. Click Close.

You should now be able to associate an experience to the Access Control Profile that was created. After the experience is published, navigating to it should go through the ADFS sign-on workflow.


Page last updated on 16 Apr 2020