jessepeterson / mdmb Goto Github PK

Consider a "server" mode whereby mdmb sits running waiting to be driven by HTTP calls instead of CLI invocations.

Use a worker/concurrency system for enrolling, like what happens for Connecting currently.

Currently to install a profile you need to have it downloaded as a file. Add support for calling out to a URL, maybe even with a parameter of the device UUID to retrieve a dynamic profile.

Support OTA & ADE (DEP) enrollment. This is of dubious value due to the limitations mentioned in the README, however for those MDM servers which can be tested (i.e. getting past the Apple device CA validation) it may still be of value.

mdmb is intended to be scriptable and fully automated. This means we should put some planning into how it can be most easily driven from scripts & other tools. This includes input as well as output considering things like the best text-based output for parsing, whether we should support JSON, both options, etc.

Support encrypted profiles targeted to the simulated devices.

Right now there's a dearth of logging and where it exists it's just stdout Println's everywhere. This needs a major redux.

I'd like the logs to be structured and leveled appropriately and also be separately logged from the normal mdmb usage. I.e. hiding most logging details by default (and instead focusing on the MDM interaction rather than the device logs).

Support configuration profiles that have been signed.

The internal/device package is.. a mess; having gone through various refactors and migrations and such. It needs a refactor & cleanup.