Fleet 4.31.0 is live. Check out the full changelog or continue reading to get the highlights. For upgrade instructions, see our upgrade guide in the Fleet docs.
Hot on the heels of Fleet’s public beta announcement for MDM, we continue to provide 🟢 Results by adding several new features in the enrollment workflow, including SAML authentication and complete support for bootstrap packages.
Authentication for device enrollments enables you to integrate the MDM enrollment process with an identity provider. With Fleet, you can configure authentication for enrollments using any identity provider service that supports custom SAML integrations, including Google Workspace, Microsoft Azure, Okta, OneLogin, and JumpCloud, to name a few. Once set up, users must authenticate against their identity provider using their credentials to successfully enroll their devices into Fleet.
In addition to Fleet Desktop, Fleet can also deliver a bootstrap software package or installer that to initiate the deployment and configuration of devices during the enrollment process. Use a bootstrap package to deploy your own configuration manager, such as Munki, Chef, or Puppet. With a seamless deployment and configuration of your preferred configuration manager on devices enrolled in Fleet, you will have more granular control and customized management of your organization's devices.
Available in Fleet Premium and Fleet Ultimate
Mutual TLS (mTLS) ensures secure and authenticated communication between two parties. Unlike traditional TLS, where only the server's identity is verified, mTLS requires both the server and the client to authenticate each other using digital certificates. This additional layer of security helps prevent unauthorized access and enhances data privacy. mTLS is often leveraged in a zero-trust networking environment, because security measures are applied regardless of whether the user or device is inside or outside the network perimeter.
Fleet is bringing 🟢 Results with support for TLS client certificates in fleetd (Orbit) to ensure secure communication to fleet. Learn more about using mTLS certificates when generating your Fleet packages.
Available in Fleet Premium and Fleet Ultimate
Take 🟠 Ownership of Fleet account roles with greater granularity. Fleet 4.31.0 includes a new user role, gitops
.
The gitops
user role is ideal for automated workflows as part of continuous integration/continuous development (CI/CD) actions, such as MDM profile commitments and security profiles. The gitops
user role can only access Fleet using the API and is unable to access the Fleet dashboard.
gitops
user role to Fleet. GitOps users are users that can manage configuration.fleetctl get mdm-commands
command to get a list of MDM commands that were executed. Added the GET /api/latest/fleet/mdm/apple/commands
API endpoint.apple_bm_enabled_and_configured
to app config responses.mdm.macos_setup.macos_setup_assistant
key in the 'config' and 'team' YAML payloads supported by fleetctl apply
.GET
, POST
and DELETE
methods on the /api/latest/fleet/mdm/apple/enrollment_profile
path).observer_can_run
queries for observers in fleetctl get queries
to match the UI behavior.changed_macos_setup_assistant
and deleted_macos_setup_assistant
activities for the macOS setup assistant setting./api/_version/fleet/logout
to return HTTP 401 if unauthorized./api/fleet/orbit/enroll
if secret is invalid.GET /api/_version_/fleet/hosts
returned when mdm_enrollment_status
is invalid.Visit our Upgrade guide in the Fleet docs for instructions on updating to Fleet 4.31.0.
Find out how Fleet can benefit your organization by exploring our docs and community.
Want to get up and running quicker? Then try out Fleet locally on your device - you’ll be up and running in minutes.