Overview

Custom Domain support allows the customers to gain complete control over the domain name that they can use for their account in Captivate Prime. A customer needs to purchase the custom domain separately and work with Adobe team to set it up as their login URL for their learning platform. 

This allows the customer to white label the login and access experience, such that the users do not see any presence of Adobe or Adobe Captivate Prime. 

For instance, you’d like to customize your domain such that your users get the same experience as if they are on the Adobe domain. If ABC Inc wants to train their customers, it would like them to land on a domain called abc.com/mylearning, instead of captivateprime.adobe.com/abc-inc/mylearning

As a pre-requisite, you must register the domain and then Adobe will guide you through customizing the url.

Notă:

Custom domain feature is available at an additional cost. Please contact your Customer Success Manager to know more details. 

<customer_custom_domain> is the customizable part.

How to setup a custom domain on an account

Notă:

As a pre-requisite, a customer must own a domain name and purchase the domain from a provider.

As an example, let us consider that a customer owns a fictitious domain, acme.com. The customer wishes Captivate Prime content to be served from learning.acme.com.

Follow the steps below to set up a custom domain.

  1. The customer has to add three CNAME records in the domain:

    • learning.acme.com: ALB public endpoint of Captivate Prime shared by Adobe
    • lrs.learning.acme.com: ALB public endpoint pointed by learning.acme.com
    • cdn.learning.acme.com: CDN endpoint shared by Adobe
  2. The customer must provide SSL certificates for these domains:

    • learning.acme.com
    • lrs.learning.acme.com
    • cdn.learning.acme.com
  3. Adobe will upload these SSL certificates to AWS ALB for serving requests to the domains.

  4. Adobe will add learning.acme.com in their SAN cert.

  5. Adobe will generate the SP metadata for the customer as the metadata will contain the custom domian URLs.

    • If the customer wishes to have social login, then Adobe must include the redirect url patterns of the social sites in the list of allowed urls.
    • If the customer has enabled SSO, then the customer must work with their IDP to include their domains in the redirect urls. The customer must share the IDP metadata XML with Adobe. Adobe then must update the SSO settings of the customer's account.
  6. Adobe will then modify the S3 CORS rules to include the customer's domain.