<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Certificate on MicroMDM</title><link>https://micromdm.io/tags/certificate/</link><description>Recent content in Certificate on MicroMDM</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 19 Dec 2019 13:03:00 +0800</lastBuildDate><atom:link href="https://micromdm.io/tags/certificate/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding MDM Certificates</title><link>https://micromdm.io/blog/certificates/</link><pubDate>Thu, 11 May 2017 13:04:37 +0200</pubDate><guid>https://micromdm.io/blog/certificates/</guid><description>&lt;p>Apple Mobile Device Management (MDM) requires the use of various digital certificates for its operation. But exactly which certificates and the various ways in which they are generated, acquired, signed, used, exported, imported, and managed within an MDM product may not be so clear. Generally speaking a commercial MDM product or service manages most of the complexity related to these certificates for you but in the case of an open source MDM much of that responsibility will land on you. In this post I hope to bring a better understanding of these certificates with the aim that you&amp;rsquo;ll be managing at least a few of them yourself.&lt;/p></description></item></channel></rss>