Skip to content

Update Jamf and macOS w/ Fleet and agent documentation#533

Open
hslatman wants to merge 4 commits into
mainfrom
herman/fleet-osquery-extension
Open

Update Jamf and macOS w/ Fleet and agent documentation#533
hslatman wants to merge 4 commits into
mainfrom
herman/fleet-osquery-extension

Conversation

@hslatman

@hslatman hslatman commented Jul 21, 2026

Copy link
Copy Markdown
Member

This PR takes the changes from #526, and builds on it by replacing the Fleet SCEP enrollment flow with an ACME enrollment flow backed by our Osquery extension. At the moment the .mobileconfig in our web console has to be tweaked manually for this flow to work: 1) Certificate to be removed; 2) CAFingerprint to be set to the SHA256 of the agents root.

Some iOS/ipadOS/tvOS references have been removed, as they seemed to be out of place in the current document. For those platforms we should either support plain SCEP (without the agent) or native ACME. It warrants an entirely new section or possibly even a page.

The updated Jamf docs have not been changed.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ hslatman
❌ JoeWagstaff
You have signed the CLA already but the status is still pending? Let us recheck it.

@hslatman
hslatman marked this pull request as ready for review July 21, 2026 16:41
@hslatman
hslatman requested a review from a team as a code owner July 21, 2026 16:41
If you plan to use GitOps instead of the Fleet UI, skip this step and see the [GitOps section below](#gitops-configure-fleet-with-fleetctl) for the YAML-based alternative.
</div>
</Alert>
Fleet deploys certificates and configuration to devices using a configuration profile. You can download this from the Smallstep dashboard and upload it to Fleet. No need to build the payloads or paste certificate data by hand.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description notes that the .mobileconfig from the web console currently still has to be tweaked manually for this flow to work — specifically (1) removing the Certificate key and (2) setting CAFingerprint to the SHA256 of the agent's root. That seems to contradict the "No need to build the payloads or paste certificate data by hand" instruction here (and the "bundles everything required" follow-up on line 147).

Should these steps document the manual Certificate removal and CAFingerprint change, or is the console expected to emit a ready-to-upload profile before this merges? Want to make sure we're not shipping instructions that won't work end-to-end yet.

(Note: the Jamf doc has the equivalent "no need to build the payloads by hand" claim on its line 136 — may warrant the same caveat if it applies there too.)

@hslatman hslatman Jul 21, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The console is expected to fill the correct info. That change won't be online before this gets tested, though. So just manual for now, and this can be merged after.

For Jamf there's no need to change it, as it still uses SCEP in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants