What can be expected?
By configuring a CNAME domain, the client is able to use their own domain and/or subdomain to access MobieTrain’s app, using it also in internal communications. For example, instead of
app.mobietrain.com, you can useacademy.clientdomain.comorclientacademy.com.The CNAME configuration can also be used with SSO integrations, with some limitations. See below.
How does it work?
The domains/subdomains should have CNAME records pointing to the following domains:
ID Portal → id-white-label.mobietrain.com
Example: id.clientacademy.com CNAME id-white-label.mobietrain.com
Example: id.clientdomain.com CNAME id-white-label.mobietrain.com
APP → app-white-label.mobietrain.com
Example: app.clientacademy.com CNAME app-white-label.mobietrain.com
Example: academy.clientdomain.com CNAME app-white-label.mobietrain.com
CMS → cms-white-label.mobietrain.com
Example: cms.clientacademy.com CNAME cms-white-label.mobietrain.com
Example: cms.academy.clientdomain.com CNAME cms-white-label.mobietrain.com
TTL should be set according to the internal policies of the company. We recommend 5 minutes.
We advise to not use proxies between the domains / subdomains and MobieTrain as we cannot guarantee they are going to work properly.
Using CNAME with SSO
When a client has an SSO integration with MobieTrain, in order to login, a link like this is used:
https://app.mobietrain.com/login/external/<client-account-slug>/<identifier>
By configuring CNAME, the link will look like:
https://academy.clientdomain.com/login/external/<client-account-slug>/<identifier>
This is the link that should always be used by the client’s users, if they have SSO configured.
Using CNAME without SSO
Using CNAME without SSO is the ideal use case for a custom domain. This will allow the client to divulge a straightforward domain to all the users.
As we can see above, using the CNAME with SSO, does not bring much added advantage in terms of link communication, since the URL, in order to work, needs to be communicated with the /login/external/… part.
If the client is not using SSO, and the users log in via the MobieTrain app, then the simple domain can be communicated and it will work as intended. E.g:
academy.clientdomain.com
What are the dependencies?
The client should own the domain/subdomain that will be used, and be able to configure the CNAME record.
What do we need from the client?
The domain should be configured by the client with CNAME records pointing to MobieTrain’s domains.
After the domain is configured, MobieTrain should be informed, in order to proceed with the configuration of our servers to accept connections from those hosts and generate the proper SSL certificates required for TLS connections.
F.A.Q.
If I have an SSO Integration with MobieTrain, can the CNAME be used? Yes. See limitations above.
Does the CNAME influence the App name? Yes. The app name is taken from the domain name. It follows these rules:
Any non letter character will be treated as a space;
Every first letter of a word will be capitalized. E.g. heroacademy.com, results in “Heroacademy”, hero-academy.com, results in “Hero Academy” app name.