Victor Vrantchan

I've thought about this a bunch, but always feel like the complexity introduced by the implementation doesn't justify the benefits. I could be proven wrong though. - The implementation right...

Another reason this is problematic. Currently `/v1/push/:udid` will accept the UDID of a managed user as well as a managed device. Users don't have serials. As I'm cleaning up the...

To add basic auth, I'd implement a new WithHeader(key, value) option in here https://github.com/micromdm/micromdm/blob/master/workflow/webhook/webhook.go Store it as a struct field on the Worker And pass it to the postWebhook function...

Same for a signing key for hmac

I've thought about this in the past and would only find it acceptable if the data was 100% segregated/provably secure between tenants. I am willing to discuss how this would...

> Would you merely want the capability for this or the de-facto requirement of it? I think "multi-tenancy" is also just a label — all the of the things above...

@chrisyeo is this ASM or another Business Manager or some other dep server?

I think Payload composition is a topic complex enough to be its own application. MicroMDM as a core service will focus on APIs to add a already built/signed profile and...

I'd be in favor of adding a CLI flag which specifies the enrollment profile ID, and changing the EnrollmentID const to use the flag if provided.

If you're cloning micromdm, it needs to go into `$GOPATH/src/github.com/micromdm/micromdm` not `~/code/micromdm` or `$GOPATH/src/github.com//micromdm` `$GOPATH/src/github.com/micromdm/micromdm` is the only project path that will work with the go compiler. $GOPATH, can be...