Victor Vrantchan

Would you expect the user to just be removed from micromdm, or would you expect it to be removed from all managed devices too?

@a-zaleski that approach works for me.

This is our plan! I am working on exposing GCP PubSub and NSQ for this functionality. If you're interested in using RabbitMQ, you can implement the pubsub interface here: https://github.com/micromdm/micromdm/blob/f7580b38bcea4a55f88eb56ddecc80183ac9e8b4/platform/pubsub/pubsub.go...

This is now supported in the library. If anyone wants to add it to `mdmctl` feel free.

Yup. The ProfileUUID is not even referenced in the API call. I tested this, its pretty useful.

Yes that's correct. If you're looking to work on this, I suggest adding a `--basic-auth` flag to get the hang of it. You can see how it's done in [micromdm/squirrel](https://github.com/micromdm/squirrel/blob/e0bca95d58925b0d3f961f509b69fd6fa5ad746d/cli/serve.go#L170-L181)...

Hi @np5, Thanks for the detailed comment. I was speaking with someone else about the OTA 2 step profiles recently. We should definitely work on supporting that mechanism. As far...

> I am not aware of any other way to authenticate the user. If you request a basic auth though, you would get the actual username and password and could...

Two questions/concerns: 1) Can we get some data regarding performance and wether individual queues are a problem today? 2) How would commands be tracked? Currently each queued command has a...

> However, we found that the current boltdb implementation may not be reliable enough. I'm curious, did you find this through any sort of testing? What was the criteria for...