Closed tomsik-radek closed 7 months ago
Error: POST /api/latest/fleet/mdm/apple/request_csr received status 422 Validation Failed: this email address is not valid: Bad Request
Sorry to see you have having issues. This certificate requires an email that is a work email
and not a personal email so it can't be @gmail / yahoo / hotmail etc
Please let me know if you have any other questions.
Putting https://[redacted]:8080/api/latest/fleet/version into browser returns "message": "Authorization header required", which seems correct
This is correct, the UI is supplying the auth header explicitly for each api call and not as a cookie so just opening this in the browser does not work by design. You can get the server version information easily from the My Account
page in the ui at /account
Error: POST /api/latest/fleet/mdm/apple/request_csr received status 422 Validation Failed: this email address is not valid: Bad Request
Sorry to see you have having issues. This certificate requires an email that is a
work email
and not a personal email so it can't be @gmail / yahoo / hotmail etcPlease let me know if you have any other questions.
Putting https://fleet.[redacted]:8080/api/latest/fleet/version into browser returns "message": "Authorization header required", which seems correct
This is correct, the UI is supplying the auth header explicitly for each api call and not as a cookie so just opening this in the browser does not work by design. You can get the server version information easily from the
My Account
page in the ui at /account
Thanks for a quick answer Suggestion: That email limitation should REALLY be mentioned in the docs. Also, maybe it should say "Yes, it says Apple, but this is used for Windows as well."
Second: Why is it limited to work accounts? This is on my server, at home, self hosted, in a homelab. I can create a Fleet admin account with a Google email address, so why can't I use MDM with it?
As for the API link, I'm aware. I just mentioned it to make it clear that "yes, the API is visible from the outside"
Absolutely understandable. I tracked down the original feature work and will open a PR to add a summary of this to the documentation.
Here are the lists of emails that are currently blocked https://github.com/fleetdm/fleet/blob/d5df23964b0b52f1d442b66ffe4451dc2a9ef969/website/api/controllers/deliver-apple-csr.js#L60 and the reasoning is ultimately based on https://mdmcert.download/about
Why is my email address not allowed? We block most free and disposable email accounts as a measure to prevent individual use and personal devices. This is a requirement from Apple.
I'll go ahead and close this issue when the Documentation update is merged. Please let me know if there is anything else you needed here.
@georgekarrv Would you be willing to edit your comment? I forgot my domain name there. Thanks. Otherwise this can be closed.
Windows MDM keys untamed, Fleet's issue, now resolved, named. In a cloud city, no blame.
Fleet version: fleetctl - version 4.47.1
Web browser and operating system: Windows 11 23H2, Firefox 123.0.1
Fleet server is running on Alma Linux 9.3, installed using the CentOS guide. Valid certificate via Letsencrypt, port 8080 port forwarded.
💥  Actual behavior
When attempting to create https://fleetdm.com/guides/windows-mdm-setup, I get the following error
Error: POST /api/latest/fleet/mdm/apple/request_csr received status 422 Validation Failed: this email address is not valid: Bad Request
Result of
fleetctl generate mdm-apple --email [redacted]@gmail.com --org [redacted] --debug