kitzy
efa9cf9bdf
Adds `docs/solutions/api-scripts/sync_jamf_users_to_fleet.py`, a Python script that: - Scrapes every computer in Jamf Pro via the Classic API (`/JSSResource/computers/subset/basic`) - Pulls the assigned user's email (falls back to username if no email is set) - Matches each device to a Fleet host by serial number - Assigns that user to the host in Fleet via `PUT /api/v1/fleet/hosts/:id/device_mapping` Features: - Supports both OAuth 2.0 client credentials and username/password auth for Jamf - `--dry-run` flag to preview changes without modifying Fleet - Summary statistics on completion (assigned, skipped, errors) Resolves fleetdm/confidential#14972
Solutions
Best Practices
General
- Name the file what the profile does.
- For example, instead of
googlePlayProtectVerifyApps.json(the name of the Android policy for this control), describe what it does:enforce-google-play-protect.json.
- For example, instead of
- Use kebab case in file names, with all letters in lowercase.
- Instead of
passwordPolicy.json, usepassword-policy.json.
- Instead of
- Be sure to end files with an empty newline.
symlinks
If a solution is applicable to multiple platforms, keep the original in the main platform directory and symlink it to the other platforms. For example, if an Apple configuration profile can be used on both macOS and iOS, use macOS as the source, and create a symlink in the iOS directory.
cd docs/solutions/ios-ipados/configuration-profiles/- Note that this is the destination that we want the symlink to be in.
ln -s ../../macos/configuration-profiles/my-profile.mobileconfig .- The
.here at the end means the current directory, and will use the same file name as the original (which is what we want).
- The
git add profile.mobileconfiggit commit