Jamf-Concepts/the-onboarding-tool v2.6.3-beta

v2.6.3 Beta

on GitHub

The Onboarding Tool 2.6.3 Beta

This beta lets you import configuration profiles, so you can download a profile from Jamf Pro, edit it in TOT, and export it again. It also makes the Jamf Pro API client connection more reliable and fixes a sidebar button that the scroll bar could cover.

This is a beta. Test it before using it for production profiles, and report anything that looks wrong on GitHub Issues.

Install: download TheOnboardingTool-2.6.3.pkg below. It installs over 2.6.2.

Supported versions: Setup Checklist 1.1 and Setup Manager 1.4.7 (with Installomator v10.9). Requires macOS 15 or later.

Highlights

• Import configuration profiles: Import accepts .mobileconfig files, including profiles downloaded from Jamf Pro, as well as .plist
• Profile Name on export, so every .mobileconfig export uploads to Jamf Pro as a new profile without a name clash
• Export Setup Checklist and Welcome as one profile
• More reliable API client connections, with clearer errors when Jamf Pro refuses the connection

Configuration profile import

• Import (the toolbar button in both modules) and paste in Plist Preview now accept .mobileconfig as well as .plist, signed or unsigned
• Profiles downloaded from Jamf Pro import directly. TOT removes the signature to read the settings; it doesn't verify it. Jamf Pro signs the profile again when you upload it
• Reads Application & Custom Settings payloads, including Set-Once and Often settings, as well as profiles exported from TOT
• Other payloads are skipped, such as Privacy Preferences (PPPC) or notifications. TOT lists them after import so you can add them back in Jamf Pro
• A profile with both Setup Checklist and Welcome settings imports both
• Importing a profile into the wrong module tells you which settings the profile contains
• When Jamf Pro keeps a hidden second copy of a payload, TOT imports the one Jamf Pro shows

Export

• Profile Name: the .mobileconfig save panel asks for the profile name, prefilled with the default name plus the date and time. Jamf Pro rejects a profile whose name or identifier matches an existing one, so every export is a new profile. To change a profile that's already in Jamf Pro, edit it there, or upload the new export and retire the old one
• Export Checklist and Welcome as .mobileconfig: new first item in the Setup Checklist export menu, one profile laid out the way Jamf Pro's own download is. Exporting each tab separately still works

Jamf Pro connection

• API client credentials are sent with strict encoding. A client secret containing characters such as +, &, or = could be changed before Jamf Pro read it, which made the connection fail (#4)
• Spaces and line breaks pasted around a client ID or secret are ignored
• Clearer errors: Test Connection shows Jamf Pro's reason and what to check, for example "Jamf Pro didn't accept the client ID or secret. Check both, and that the API client is enabled in Jamf Pro." You can select the message and copy it
• A hostname alone works in Server URL, for example yourorg.jamfcloud.com. TOT always connects over HTTPS: it adds https:// if you leave it off and upgrades http://
• If a token request is redirected, TOT stops and tells you where it pointed, instead of failing with an unclear error
• API client connections use Jamf Pro's documented token endpoint
• Debug logging records the length of the client ID and secret, never their values, to help with troubleshooting

Fixes

• The Add (+) button in the sidebar could be covered by the scroll bar once the Actions or Steps list was long enough to scroll (#5). It now sits next to the count
• A blank API client ID or secret no longer produces an unclear "Unexpected response format" error

Known issues

• Pasting a profile into Plist Preview skips other payloads without listing them. Use Import for the list
• Setup Manager's grid view can open a category collapsed on a fresh install. Click the chevron to expand it