Configuring SAML for Media Shuttle

Media Shuttle supports authentication using SAML 2.0 compatible identity providers to allow portal members to use Single Sign-On (SSO). To use an external identity provider with Media Shuttle, both Media Shuttle and your identity provider require configuration so that they communicate using SAML.

In Media Shuttle you must configure your Configuration Type, Service Provider Metadata, Domain Restrictions and Identity Provider Metadata.

Metadata Configuration Files

In establishing the trust between the service provider and the identity provider, there are two metadata configuration files:

  • Service Provider Metadata: This file allows the identity provider to know the request is originating from an authorized service provider. The service provider metadata file also provides the location to which users are returned after authenticating through the identity provider.

    Note: Some identity providers accept a Service Provider Metadata URL. Others require you to input service provider metadata manually. For configuration details, see Service Provider Metadata.

  • Identity Provider Metadata: This file tells Media Shuttle where to send the user to be authenticated. Its information is stored within Media Shuttle. The metadata can be updated by referencing the file again and selecting Save Changes.

    Note: The identity provider metadata must include an HTTP-Post login service location. HTTP-Redirect services are not supported.

    <md:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location=""/>

To configure SAML for Media Shuttle:

  1. In the Account Administration console, click Security.
  2. Under Authentication, select Login is required.
  3. Under Authentication type, select SAML 2.0.
  4. Select a configuration type:

    • Account level: Configure access to all existing portals and any new portals with the same SAML authentication settings.
    • Portal level: Configure access to portals with SAML on an individual basis.
  5. Add Media Shuttle's Service Provider Metadata to your identity provider.

    • If your identity provider accepts a URL, copy and paste the metadata link.
    • If your identity provider requires you to input metadata, open the link in your browser and copy the properties from the XML file.
  6. Select domain restrictions:

    • Unrestricted domains: Uses the same identity provider for all portal members and administrators authenticating with SAML.
    • Restricted domains: Allows you to require SAML authentication for users from specified email domains. Users from all other domains will be authenticated through Media Shuttle. You can also select Configure identity provider for all other users to specify that users from other domains require authentication by another identity provider.
  7. Enter your Sign in display name. By default, the displayed text is "Sign in with SAML".
  8. Ensure that Auto-add SAML authenticated members to this portal is selected to give all authenticated members access to Media Shuttle. If this option is disabled, membership is controlled by the portal administrator.
  9. Specify your Identity Provider Metadata by pasting in the identity provider's metadata URL or by clicking Browse and selecting the XML file that contains the identity provider's metadata.
  10. Click Save Changes.

Service Provider Metadata

Some identity providers do not accept a Service Provider Metadata URL. If you are required to input the metadata, refer to the following configuration information to make your SAML identity provider compatible with Media Shuttle.

Account level configuration

Single Sign-on URL:
Audience URI (SP Entity ID): mediashuttle
Name ID format: Email Address
Application Username: Email

Advanced Settings
Enable Single Logout: Allow application to initiate Single logout Single Logout URL:
SP Issuer: mediashuttle
Signature Certificate: X509 Certificate, which can be found in your service provider metadata

Attribute Statements
Name Format: Unspecified

Portal level configuration

Single Sign-on URL: https://<Portal URL>/auth
Audience URI (SP Entity ID): https://<Portal URL>/
Name ID format: Email Address
Application Username: Email

Advanced Settings
Enable Single Logout: Allow application to initiate Single logout
Single Logout URL: https://<Portal URL>/auth
Signature Certificate: X509 Certificate, which can be found in your service provider metadata

Attribute Statements
Name Format: Unspecified

Example of SAML Response


<Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion">

  <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Success" />

<Assertion  ID="_0edfeecb-d4b9-4c05-94b1-87f481fbef5f"


<ds:Signature xmlns:ds="">

  <ds:CanonicalizationMethod Algorithm="" />
  <ds:SignatureMethod Algorithm="" />
  <ds:Reference URI="#_0edfeecb-d4b9-4c05-94b1-87f481fbef5f">
      <ds:Transform Algorithm="" />
      <ds:Transform Algorithm="" />
    <ds:DigestMethod Algorithm="" />


<KeyInfo xmlns="">

  <NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:transient">
  <SubjectConfirmation Method="urn:oasis:names:tc:SAML:2.0:cm:bearer">
    <SubjectConfirmationData NotOnOrAfter="2014-05-13T13:47:26.698Z"

<Conditions NotBefore="2014-05-13T13:42:26.695Z" NotOnOrAfter="2014-05-13T14:42:26.695Z">

  <Attribute Name="">
  <Attribute Name="">
    <AttributeValue> </AttributeValue>
  <Attribute Name="">
  <Attribute Name="">
    <AttributeValue>Test User</AttributeValue>
  <Attribute Name="">
  <Attribute Name="">
  <Attribute Name="">
    <AttributeValue>Domain Users</AttributeValue>

<AuthnStatement AuthnInstant="2014-05-13T13:42:13.933Z"