White Labeling the iOS, macOS, and Android enrollment pages
Getting Started
This article explains how to customize the enrollment page for iOS, macOS (MDM), and Android devices - the enrollment page is what is made visible for your end users when they enroll their devices manually (BYOD or manual enrollment).
Hosted FileWave customers: These enrollment-page templates live on the FileWave Server filesystem. Self-managed customers with server access can edit the files directly. If your FileWave Server is hosted by FileWave, contact FileWave Technical Support for assistance with hosted-server template changes.
| Feature | Customization type | Technology |
|---|---|---|
| iOS, macOS MDM, Android | Server template | HTML |
| Managed Platform | Server Platform | Location |
| Android | macOS and Linux | /usr/local/filewave/django/user_templates/android/welcome.html |
| iOS and macOS | macOS and Linux | /usr/local/filewave/django/user_templates/ios/welcome.html |
This HTML document is actually a template, containing variables that will be replaced by the real values when processed by the FileWave server. We are using Django template language - but in a very limited way; only a few variables are important.
iOS and MacOS
| variable | usage |
|---|---|
static |
Path where FileWave stores static files like icons, css files |
<already_trusted_ca |
True if the server has a valid, trusted SSL certificate |
The template will show one or two steps depending on the SSL certificate your server is using.
In case of self signed certificate:
- step 1 is to download the certificate (to be manually installed in the device trust store); link must point to "/CA"
- step 2 is to enroll the device; link must point to "/enroll"
In case of trusted certificate (recommended):
- step 1 is to enroll the device; link must point to "/enroll"
Android
| variable | usage |
|---|---|
static |
Path where FileWave stores static files like icons, css files |
filewave_version |
FileWave server current version. "12.4.0" for instance |
| server_host | FileWave server FQDN as set in preferences. "server.filewave.ch" for instance |
| server_port | FileWave server port as set in preferences. 20443 by default. |
Android template always shows two steps:
- step 1 is to download FileWave Android Native App Portal on FileWave CDN, using filewave_version variable. You may want to change this link if you have a custom Android Native App Portal.
- step 2 is to automatically configure the Android Native App Portal, once it has been installed, using server_host and server_port variables.
Additional files
Additional files can be placed in the same directory and will be served with the /user_templates/ios/ prefix. For instance, if you want to include a CSS file, you can add to your index.html:
<link rel='stylesheet' href="/user_templates/ios/enroll.css" />And copy "enroll.css" in the same directory as index.html.