Victor Vrantchan
Victor Vrantchan
### What version of `micromdm` are you using? 1.3.1 Scheduling a command is all good and dandy, but your cert is expired you'll never know about it. Provide a way...
The enrollment URL is accessible through two separate methods: DEP devices send a `POST`: - because of restrictions with DEP we can only issue a 401 with`WWW Authenticate` here. Support...
This scenario fails a bit right now: - termination is done by proxy and certificates are self signed. Mainly because `-tls=false -tls-cert=/path/to/cert` flips tls to `true`. Beside that I was...
To support this, an external SCEP service should be supported. The user will have to stand up `micromdm/scep` as a separate server or use microsoft's or any of the other...
all the actions in MDM are built around a specifc UDID. Imagine your devices UDID suddenly changes, this breaks MDM unless we use the internal UUID of the device, and...
MicroMDM has a robust set of APIs for scheduling commands, reading device data and managing the server itself. The documentation for these should be exposed with Swagger or similar REST...
If `mdmctl` uploads a certificate, we should first check if one is already there and warn the user. Print out the current certificate info (expiration & topic) and then tell...
``` ts="2017/11/17 21:01:44" caller="http2: Transport failed to get client conn for mdmenrollment.apple.com:443" msg="http2: no cached connection was available" level=info msg="serving HTTPS using provided certificates" addr=:https ts="2017/11/17 21:01:44" caller="http2: Transport failed...
allow the user to specify the path to the configuration, which is `~/.micromdm/servers.json` right now. Needs a new CLI flag and env var which would override the config path. Loading...
From @jessepeterson in #199 > I'd make a note in the flag arguments that -sign requires productbuild (even though it compiles out of the linux binaries). > Perhaps we should...