Checklist
Introduction
After you have completed the installation, here is a list of small tasks you can go through to make sure your installation works as expected.
Login
System Administrator
The system administrator can be used to create additional organizations.
You can log in to Relution as a System Administrator by using the
credentials defined in the application.yml or in the environment variables.
application.yml
relution:
system:
admin:
password: ""
email: ""
**Environment variables
SYSTEM_ADMIN_PASSWORD=""
SYSTEM_ADMIN_EMAIL=""
Organization administrator
You can log in to Relution as an organization administrator. If you are using LDAP, make sure you can log in with at least one LDAP user account.
| Test | Result |
|---|---|
| Logging in with a local account is possible | |
| Logging in with an LDAP account is possible |
For security reasons, we strongly recommend that you change your password after the first login to change it.
Certificates
Make sure you can connect to Relution using the external hostname. Mobile devices can be stricter when it comes to verifying SSL certificates. Even if your desktop browser shows a valid HTTPS connection, the devices may reject the connection if some things are not configured properly. We strongly recommend using SSL Labs → to verify that everything is set up correctly.
| Test | Result |
|---|---|
| You can open https://${hostname} in the browser | |
| The browser displays a secure connection. (Chrome, Edge, Firefox, Safari) | |
| SSL Labs → does not display any warnings or errors |
Common errors.
Incomplete certificate chain (missing intermediate certificates). Chrome, Firefox, etc. can ignore this, but mobile devices may reject the connection.
Reverse proxy uses server name indication (SNI). This is not supported by some older Android versions. As a workaround, you should make sure that the MDM server’s certificate is the first one returned.
Mobile devices reject the certificate
Possible Cause.
- The certificate chain may be incomplete. An incomplete chain is ignored by most desktop browsers, but may cause errors on mobile devices.
Solution
- Use SSL Labs → to verify that your SSL Certificate is set up correctly. It takes about 5 minutes for the test is complete. Fix any issues that are reported.
Mobile devices receive a different certificate
Possible Cause.
- The server may be using Server Name Indication (SNI), which is not supported by all mobile devices.
Solution
- Reconfigure the web server so that the first certificate returned is the one required by the mobile devices. The devices are not able to request a specific certificate and always use the first one sent by the server.
Database backups
Make sure you have a working database backup. This is important in case the hardware fails or an upgrade goes wrong.
| Test | Result |
|---|---|
| Relution’s database is included in automatic backups | |
| You can restore the database (on another computer) |
Current Relution Client Apps.
iOS
We always recommend using the Relution App Family for iOS from the public App Store. These are automatically imported into the Relution App Store.
Android
If you want to use the native version of these applications directly in Relution, you can find them here: Until Relution Server 5.10:
From Relution Server 5.11:
Support
For support purposes, you may want to allow remote access to your Relution server. Consider enabling or installing remote access software such as Remote Desktop, SSH or TeamViewer. For the best possible security we recommend using SSH with key-based authentication.
Consider using a separate user account for support personnel (e.g., for audit purposes). The support staff usually needs read and write access to the installation directory and the ability to restart the Relution service. Relution service to restart.