Jump to content

MDM https requirements

Recommended Posts


I want to use my wildcard certificat that looks like *.my-domain.com (it does not contain the CommonName or subjectAltNames matching the MDM hostname)  for enrollment devices process,

But when i read the requirements here https://help.eset.com/era_install/65/en-US/certificate_mdm_https_requirements.html,

the CommonName or subjectAltNames must match the MDM hostname
 validation-status-icon-infoNOTE:  If the MDM hostname is , for example hostname.mdm.domain.com, your certificate can contain names like:
But not names like :

I think my wildcard it's not supported ?

Best regards,

Link to comment
Share on other sites

  • ESET Staff


Those requirements are there mainly because iOS devices as we use built-in iOS. What iOS devices accept as trusted differs per iOS version and we described _most_ restrictive rules which should work always. (There are other requirements like RSA2048+, SHA256+ etc... for iOS described elsewhere in documentation)

So in the end Your certificate may work (it will definitely work for Android devices), however when Apple brings some update to their trust validation it might stop working.



Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...