Hello there!

Need Help? We are right here!

miniorange Support~
miniOrange Email Support
success

Thanks for your Enquiry.

If you don't hear from us within 24 hours, please feel free to send a follow-up email to info@xecurify.com

Search Results:

×

Brightcove Single Sign-On SSO


Single Sign-On (SSO) solution by miniOrange provides secure Single Sign-On access into Brightcove using a single set of login credentials. You can log into Brightcove using miniOrange credentials or Azure AD credentials or any of your existing identity providers. With miniOrange SSO services, along with Brightcove you can also login into other On-Premise and Cloud Applications using your existing Identity Providers/User Store (Azure Active Directory, Okta, Ping) credentials. Follow the given setup guide to integrate SAML SSO for your Brightcove account.


miniOrange and Brightcove Single Sign-On (SSO) integration supports the following features:


  • SP Initiated Single Sign-On (SSO)
  • IdP Initiated Single Sign-On (SSO)

Connect with External Source of Users


miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, OpenLDAP, AWS etc), Identity Providers (like Microsoft Entra ID, Okta, AWS), and many more. You can configure your existing directory/user store or add users in miniOrange.



Follow the Step-by-Step Guide given below for Brightcove Single Sign-On (SSO)

1. Configure Brightcove in miniOrange

  • Login into miniOrange Admin Console.
  • Go to Apps and click on Add Application button.
  • Brightcove Single Sign-On (SSO) add app

  • In Choose Application, select SAML/WS-FED from the application type dropdown.
  • Brightcove Single Sign-On (SSO) choose app type

  • Search for Brightcove in the list, if you don't find Brightcove in the list then, search for custom and you can set up your application in Custom SAML App.
  • Brightcove Single Sign-On (SSO) manage apps

  • Enter the SP Entity ID or Issuer and ACS URL. These are listed in the SSO section of the Access Control Profiles table.
    (Note: The ACS URL defaults to https://auth.bcvp0rtal.com/login/callback. You can also override the ACS URL by providing your own URL. Both of these options can be used for configuring stricter SSO providers. For existing sites, http(s)://{site-root-url}/login/callback will still work but Brightcove recommends that publishers use https://auth.bcvp0rtal.com/login/callback. This endpoint takes care of forwarding SAML data to the correct site for any sites that use a path on a domain.)
  • Brightcove Single Sign-On (sso) Brightcove Dashboard

  • Click on Next to proceed further.
  • Configure Brightcove Single Sign-On (SSO)

  • In the Attribute Mapping tab configure the following attributes as shown in the image below.
  • Brightcove Single Sign-On (sso) Add Attribute

  • Click on Save.
  • Get IdP Metadata Details to upload to brightcove:

  • Go to Apps >> Manage Apps.
  • Search for your app and click on the select in action menu against your app.
  • Click on Metadata to get metadata details, which will be required later. Click on Show SSO Link to see the IDP initiated SSO link for Brightcove.
  • Go to Metadata link Brightcove SAML SSO

  • Here you will see 2 options, if you are setting up miniOrange as IDP copy the metadetails related to miniOrange, if you required to be authenticated via external IDP's(okta,AZURE AD, ADFS, ONELOGIN, GOOGLE APPS) you can get metadata from the 2nd Section as shown below.
  • Brightcove Single Sign-On (sso) Add SAML Application

  • Keep SAML Login URL , SAML Logout URL and click on the Download Certificate button to dowmload certificate which you will require in Step 2.
  • Brightcove Single Sign-On (SSO) Select Metadata details external IDP or miniOrange as IDP

2. Configure SSO in Brightcove

  • Log in to Brightcove Gallery with your administrator account.
  • You need to select the Gallery where you want to change the login settings. In the top right corner select Gallery in the dropdown.
  • Click on the Settings tab.
  • In the left sidebar select Access Control Profiles and click Create Profile.
  • Enter SSO as a name or any other name as per your choice.
  • Check SSO - Requires a username and password for access.
  • If you have an export file of your SAML 2.0 metadata, click Select File and upload the SAML metadata file (X.509 Certificate) you downloaded in the Step 1. This will prefill the SAML 2.0 Endpoint and the X.509 Certificate fields.
  • Enter a value for the SAML 2.0 Endpoint (HTTP).
  • Enter a value for the X.509 Certificate you downloaded in the Step 1.
  • (Optional) Enter the SAML Issuer / Entity ID Override. Enter a value here to optionally override the SAML issuer.
  • Input your custom domain to field ACS URL Override. If you don't have a domain, go to Custom Domain and SSL and create a new one (enable SSL for this domain).
  • (Optional) Enter the SAML AuthnContext Override. Enter a value here to optionally override the SAML AuthnContext.
  • (Optional) Choose to disable the Default AuthnContext. By default, for SSO profiles, Gallery will send PasswordProtectedTransport as SAML authentication context. Sometimes this is not supported by the Identity providers. When this option is checked, Gallery will not send the the authentication context request.
  • (Optional) Enter any SAML attributes for that you want passed to your external JavaScript.
  • (Optional) Check Expose all attributes to expose all of the SAML attributes for use in external JavaScript.
  • Click Save.
  • Brightcove Single Sign-On (sso) Setup SSO in Brightcove Dashboard

3. Test SSO Configuration

Test SSO login to your Brightcove account with miniOrange IdP:

    Using SP Initiated Login

    • Go to your Brightcove URL, here you will be either asked to enter the username or click on the SSO link which will redirect you to miniOrange IdP Sign On Page.
    • Brightcove Single Sign-On (SSO) login

    • Enter your miniOrange login credential and click on Login. You will be automatically logged in to your Brightcove account.

    Using IDP Initiated Login

    • Login to miniOrange IdP using your credentials.
    • Brightcove Single Sign-On (SSO)

    • On the Dashboard, click on Brightcove application which you have added, to verify SSO configuration.
    • Brightcove Single Sign-On (SSO) verify configuration


    Not able to configure or test SSO?


    Contact us or email us at idpsupport@xecurify.com and we'll help you setting it up in no time.



4. Configure Your User Directory (Optional)

miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.



  • To add your users in miniOrange there are 2 ways:
  • 1. Create User in miniOrange

    • Click on Users >> User List >> Add User.
    • Brightcove: Add user in miniOrange

    • Here, fill the user details without the password and then click on the Create User button.
    • Brightcove: Add user details

    • After successful user creation a notification message "An end user is added successfully" will be displayed at the top of the dashboard.
    • Brightcove: Add user details

    • Click on Onboarding Status tab. Check the email, with the registered e-mail id and select action Send Activation Mail with Password Reset Link from Select Action dropdown list and then click on Apply button.
    • Brightcove: Select email action

    • Now, Open your email id. Open the mail you get from miniOrange and then click on the link to set your account password.
    • On the next screen, enter the password and confirm password and then click on the Single Sign-On (SSO) reset password button.
    • Brightcove: Reset user password
    • Now, you can log in into miniOrange account by entering your credentials.

    2. Bulk Upload Users in miniOrange via Uploading CSV File.

    • Navigate to Users >> User List. Click on Add User button.
    • Brightcove: Add users via bulk upload

    • In Bulk User Registration Download sample csv format from our console and edit this csv file according to the instructions.
    • Brightcove: Download sample csv file

    • To bulk upload users, choose the file make sure it is in comma separated .csv file format then click on Upload.
    • Brightcove: Bulk upload user

    • After uploading the csv file successfully, you will see a success message with a link.
    • Click on that link you will see list of users to send activation mail. Select users to send activation mail and click on Send Activation Mail. An activation mail will be sent to the selected users.

5. Adaptive Authentication with Brightcove

A. Restricting access to Brightcove with IP Blocking

    You can use adaptive authentication with Brightcove Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.

    You can configure Adaptive Authentication with IP Blocking in following way:
  • Login to Self Service Console >> Adaptive Authentication.
  • Add a Policy Name for your Adaptive Authentication Policy.
  • Brightcove Single Sign-On (SSO) Restrict Access adaptive authentication policy

  • Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.
  • Brightcove Single Sign-On (SSO) Restrict Access adaptive authentication behavior change


    Action for behavior Change Options :


    Attribute Description
    Allow Allow user to authenticate and use services if Adaptive authentication condition is true.
    Challenge Challenge users with one of the three methods mentioned below for verifying user authenticity.
    Deny Deny user authentications and access to services if Adaptive authentication condition is true.

    Challenge Type Options :

    Attribute Description
    User second Factor The User needs to authenticate using the second factor he has opted or assigned for such as
  • OTP over SMS
  • PUSH Notification
  • OTP over Email
  • And 12 more methods.
  • KBA (Knowledge-based authentication) The System will ask user for 2 of 3 questions he has configured in his Self Service Console. Only after right answer to both questions user is allowed to proceed further.
    OTP over Alternate Email User will receive a OTP on the alternate email he has configured threw Self Service Console. Once user provides the correct OTP he is allowed to proceed further.

  • Now Enable Enable IP Restriction option from the IP RESTRICTION CONFIGURATION section to configure custom IP range.
  • Brightcove Single Sign-On (SSO) Restrict Access adaptive authentication ip blocking

  • Select the Action you want to perform if the IP address is out of the range. i.e. Allow, Challenge & Deny.
  • Specify the IP Address range for which you want above setting to reflect. You can add more than one IP Address ranges by clicking on following button +.
  • Scroll to the end and click on save.

B. Adaptive Authentication with Limiting number of devices.

    Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.

    You can configure Adaptive Authentication with Device Restriction in following way

  • Login to Self Service Console >> Adaptive Authentication.
  • Add a Policy Name for your Adaptive Authentication Policy.
  • Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.
  • Brightcove Single Sign-On (SSO) Restrict Access adaptive authentication behavior and challenge type


  • Scroll down to Device Configuration section and enable Allow User to Register Device option to allow users to register their devices.
  • Enter the Number of Devices which are allowed to register in field next to Number of Device Registrations Allowed
  • Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
    1. Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
    2. Deny : Deny users access to the system
  • Enable option Send email alerts to Users if number of Device registrations exceeded allowed count if you want to alert the user about no of devices exceeding the limit. Save the configuration.
  • Brightcove Single Sign-On (SSO) Restrict Access adaptive authentication enable device restriction


C. Add Adaptive Authentication policy to Brightcove.

  • Login to Self Service Console >> Policies.
  • Click on Edit option for predefined app policy.
  • Brightcove Single Sign-On (sso) edit device restriction policy

  • Set your application name in the Application and select password as Login Method.
  • Enable Adaptive Authentication on Policy page and select the required restriction method as an option.
  • From Select Login Policy dropdown select the policy we created in last step and click on save.
  • Brightcove Single Sign-On (SSO) Restrict Access save device restriction policy

    D.Notification and Alert Message.

      This section handles the notifications and alerts related to Adaptive Authentication.It provides the following options :

    • Get email alerts if users login from unknown devices or locations : Admin need to enable this option to enable receiving alerts for different alert options.
      adaptive authentication Action for behavior Change Configuration

    • Option Description
      Challenge Completed and Device Registered Enabling this option allows you to send an email alert when an end-user completes a challenge and registers a device.
      Challenge Completed but Device Not Registered Enabling this option allows you to send an email alert when an end-user completes a challenge but do not registers the device.
      Challenge Failed Enabling this option allows you to send an email alert when an end-user fails to complete the challenge.


      adaptive authentication Action for behavior Change Configuration

    • Next subsection is Send email alerts which allows us to enable or disable alerts for admin and end-users. To enable alerts for admins, you can enable the “Administrators” switch button.

    • adaptive authentication Action for behavior Change Configuration

    • In case you want multiple admins accounts to receive alerts then you can enable the option for admin and then enter the admin emails separated by a ‘,’ in the input field next to Administrators email to receive alerts label. To enable alerts for the end-users, you can enable the “End Users” switch button.
    • In case you want to customize the deny message that end user receive in case his authentication denied due to adaptive policy, you can do this by entering the message inside “Deny message for Adaptive Authentication” text box.
    • adaptive authentication Action for behavior Change Configuration
    How to add a trusted Device
    1. When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.

External References

Want To Schedule A Demo?

Request a Demo
  

  • India+91
  • United States+1
  • Afghanistan+93
  • Albania+355
  • Algeria+213
  • American Samoa+1684
  • Andorra+376
  • Angola+244
  • Anguilla+1264
  • Antigua and Barbuda+1268
  • Argentina+54
  • Armenia+374
  • Aruba+297
  • Australia+61
  • Austria+43
  • Azerbaijan+994
  • Bahamas+1242
  • Bahrain+973
  • Bangladesh+880
  • Barbados+1246
  • Belarus+375
  • Belgium+32
  • Belize+501
  • Benin+229
  • Bermuda+1441
  • Bhutan+975
  • Bolivia+591
  • Bosnia and Herzegovina+387
  • Botswana+267
  • Brazil+55
  • Brunei Darussalam+673
  • Bulgaria+359
  • Burkina Faso+226
  • Burundi+257
  • Cambodia+855
  • Cameroon+237
  • Canada+1
  • Cape Verde+238
  • Cayman Islands+1345
  • Central African Republic+236
  • Chad+235
  • Chile+56
  • China+86
  • Colombia+57
  • Comoros+269
  • Congo (DRC)+243
  • Congo (Republic)+242
  • Cook Islands+682
  • Costa Rica+506
  • Côte d'Ivoire+225
  • Croatia+385
  • Cuba+53
  • Cyprus+357
  • Czech Republic+420
  • Denmark+45
  • Djibouti+253
  • Dominica+1767
  • Dominican Republic+1809
  • Ecuador+593
  • Egypt+20
  • El Salvador+503
  • Equatorial Guinea+240
  • Eritrea+291
  • Estonia+372
  • Ethiopia+251
  • Faroe Islands+298
  • Fiji+679
  • Finland+358
  • France+33
  • French Polynesia+689
  • Gabon+241
  • Gambia+220
  • Georgia+995
  • Germany+49
  • Ghana+233
  • Gibraltar+350
  • Greece+30
  • Greenland+299
  • Grenada+1473
  • Guadeloupe+590
  • Guam+1671
  • Guatemala+502
  • Guernsey+44
  • Guinea+224
  • Guinea-Bissau+245
  • Guyana+592
  • Haiti+509
  • Honduras+504
  • Hong Kong+852
  • Hungary+36
  • Iceland+354
  • India+91
  • Indonesia+62
  • Iran+98
  • Iraq+964
  • Ireland+353
  • Isle of Man+44
  • Israel+972
  • Italy+39
  • Jamaica+1876
  • Japan+81
  • Jersey+44
  • Jordan+962
  • Kazakhstan+7
  • Kenya+254
  • Kiribati+686
  • Kuwait+965
  • Kyrgyzstan+996
  • Laos+856
  • Latvia+371
  • Lebanon+961
  • Lesotho+266
  • Liberia+231
  • Libya+218
  • Liechtenstein+423
  • Lithuania+370
  • Luxembourg+352
  • Macao+853
  • Macedonia+389
  • Madagascar+261
  • Malawi+265
  • Malaysia+60
  • Maldives+960
  • Mali+223
  • Malta+356
  • Marshall Islands+692
  • Martinique+596
  • Mauritania+222
  • Mauritius+230
  • Mexico+52
  • Micronesia+691
  • Moldova+373
  • Monaco+377
  • Mongolia+976
  • Montenegro+382
  • Montserrat+1664
  • Morocco+212
  • Mozambique+258
  • Myanmar (Burma)+95
  • Namibia+264
  • Nauru+674
  • Nepal+977
  • Netherlands+31
  • New Caledonia+687
  • New Zealand+64
  • Nicaragua+505
  • Niger+227
  • Nigeria+234
  • North Korea+850
  • Norway+47
  • Oman+968
  • Pakistan+92
  • Palau+680
  • Palestinian Territory+970
  • Panama+507
  • Papua New Guinea+675
  • Paraguay+595
  • Peru+51
  • Philippines+63
  • Poland+48
  • Portugal+351
  • Puerto Rico+1787
  • Qatar+974
  • Réunion+262
  • Romania+40
  • Russian Federation+7
  • Rwanda+250
  • Saint Kitts and Nevis+1869
  • Saint Lucia+1758
  • Saint Vincent and the Grenadines+1784
  • Samoa+685
  • San Marino+378
  • São Tomé and Príncipe+239
  • Saudi Arabia+966
  • Senegal+221
  • Serbia+381
  • Seychelles+248
  • Sierra Leone+232
  • Singapore+65
  • Slovakia+421
  • Slovenia+386
  • Solomon Islands+677
  • Somalia+252
  • South Africa+27
  • South Korea+82
  • Spain+34
  • Sri Lanka+94
  • Sudan+249
  • Suriname+597
  • Swaziland+268
  • Sweden+46
  • Switzerland+41
  • Syrian Arab Republic+963
  • Taiwan, Province of China+886
  • Tajikistan+992
  • Tanzania+255
  • Thailand+66
  • Timor-Leste+670
  • Togo+228
  • Tonga+676
  • Trinidad and Tobago+1868
  • Tunisia+216
  • Turkey+90
  • Turkmenistan+993
  • Turks and Caicos Islands+1649
  • Tuvalu+688
  • Uganda+256
  • Ukraine+380
  • United Arab Emirates+971
  • United Kingdom+44
  • United States+1
  • Uruguay+598
  • Uzbekistan+998
  • Vanuatu+678
  • Vatican City+379
  • Venezuela+58
  • Viet Nam+84
  • Virgin Islands (British)+1284
  • Virgin Islands (U.S.)+1340
  • Western Sahara+212
  • Yemen+967
  • Zambia+260
  • Zimbabwe+263


Our Other Identity & Access Management Products