Self Signed Certificate Error during iOS OTA Enrollment
This article shows how to resolve the certificate-trust error that can appear when you manually enroll iOS or iPadOS devices through OTA enrollment while the FileWave Server uses a self-signed certificate.
For production environments, use a publicly trusted server certificate when possible. If the server still uses a self-signed certificate, confirm its identity with your FileWave administrator before installing or trusting it. In current FileWave Central, review it under Preferences → General → SSL Certificate Management → Details; older versions showed certificate controls under Mobile. See SSL Certificate Management for the current controls.

Automated Device Enrollment can still work with this certificate state, but manual OTA enrollment may fail until the device trusts the installed root certificate.

If you keep the self-signed certificate, use the steps below on the device before starting the enrollment step. Replacing the self-signed certificate with a publicly trusted certificate avoids this manual trust workflow.
Steps to resolve when keeping a self-signed certificate

Return to the manual enrollment page and continue with Step 2 - Enroll Device. Install and approve the downloaded MDM enrollment profile, then confirm that the FileWave management profile appears in the device's management settings. The trusted certificate alone is not MDM enrollment. Follow Apple Manual Enrollment to complete the device and FileWave record checks.

No comments to display
No comments to display