fleet/tools/mdm/migration/micromdm/README.md
Jahziel Villasana-Espinoza 6816bc89f0
feat: manual MDM migration updates (#21115)
> Related issue: #20311

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files)
for more information.
- [x] Added/updated tests
- [x] Manual QA for all new/changed functionality
- For Orbit and Fleet Desktop changes:
- [ ] Orbit runs on macOS, Linux and Windows. Check if the orbit
feature/bugfix should only apply to one platform (`runtime.GOOS`).
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [x] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
2024-08-08 15:46:42 -04:00

19 lines
No EOL
704 B
Markdown

# MicroMDM webhook
A tiny server you can use as a webhook callback for the MDM migration [end user workflow](https://fleetdm.com/docs/using-fleet/mdm-migration-guide#end-user-workflow).
It will try to unenroll the device based on the device UUID/UDID by sending a `RemoveProfile`
command.
## Usage
1. Find the MicroMDM API token. For the Fly.io hosted MicroMDM server it should be in
1Password. If you're having trouble finding it, drop a message in `#g-mdm` on Slack!
2. Get the MicroMDM server URL.
3. Start the server with:
```
go run tools/mdm/migration/micromdm/main.go --api-token=$MICRO_MDM_TOKEN --url=https://micromdm.example.com
```
4. Configure Fleet to send a webhook to this server.