Fleet 3.10.0 is now available and more powerful, with the beta for agent auto-updates to better manage osquery updates on your hosts, Identity Provider-Initiated Single Sign-On for increased login flexibility, and improved server logging.
Let’s jump into the highlights:
- Agent auto-updates beta
- Identity Provider-initiated Single Sign-On
- Improved server logging
For the complete summary of changes and release binaries check out the release notes on GitHub.
Agent auto-updates beta
Updating the osquery version on your hosts helps reveal new capabilities and information from your fleet, but managing updates can be challenging. Our new self-managed agent auto-updates feature, available for Fleet Basic customers, helps you manage osquery agent versions across your fleet.
We’ve also released the beta for Orbit, Fleet’s lightweight osquery runtime and auto-updater. By default, Orbit uses the public Fleet update repository to manage auto-updates.
Identity Provider-Initiated Single Sign-On
Fleet attempts to provide power users with more options for control over their Fleet instance. We’ve introduced Identity Provider-Initiated (IdP-initiated) Single Sign-On (SSO) as a configurable option in Fleet. Turning this option on provides you, and other users of your Fleet instance, with the ability to login to Fleet straight from your configured IdP dashboard.
Please make sure to understand the risks before enabling IdP-initiated SSO. Auth0 provides a great explanation of the risks and considerations of configuring IdP-initiated SSO.
Improved server logging
Generating helpful logs is a vital tool for debugging. Fleet 3.10.0 introduces more consistent logging to assist in highlighting logs of high importance such as errors, agent enrollment, live queries, and others. Thank you William Shoemaker from Atlassian for the assistance!
Upgrading to Fleet 3.10.0
Visit our Updating Fleet guide for instructions on how to update.