mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 00:45:19 +00:00
bd3e775e67
#15565 Replace the use of the isFederated registry key with a keys that check for AAD (Azure Active Directory, now Entra ID) Federated enrollment (`isFederated`) seems to be when windows uses a Discovery MDM endpoint to get its policy and management endpoint configuration. This is always the case when a client is enrolled with fleet, so installations always show up as automatic. It's being replaced by a different key, `AADResourceID`, which appears to identify the resource that controls the automated deployment. In my tests it only appears to be populated when the computer is enrolled through automated deployments. This key appears on both Windows 10 and 11. There is a similar key, `AADTenantID`, which appears to identify the client (tenant) to the Azure cloud. I haven't seen this ID in our systems, so it is likely exclusively used in Azure. Both this key and `AADResourceID` seem to always be set at the same time, so we only check for the `AADResourceID`. I've also added documentation on the registry keys I've analyzed for future reference. |
||
---|---|---|
.. | ||
Adding-new-endpoints.md | ||
API-for-contributors.md | ||
API-Versioning.md | ||
Automatically-generating-UI-component-boilerplate.md | ||
Building-Fleet.md | ||
Committing-Changes.md | ||
Configuration-for-contributors.md | ||
Deploying-chrome-test-ext.md | ||
Enroll-hosts-with-plain-osquery.md | ||
FAQ.md | ||
File-carving.md | ||
Fleet-UI-Testing.md | ||
fleetd-development-and-release-strategy.md | ||
high-level-architecture.md | ||
Infrastructure.md | ||
MDM-custom-configuration-web-url | ||
Migrations.md | ||
README.md | ||
Releasing-Fleet.md | ||
Run-Locally-Built-Fleetd.md | ||
Seeding-Data.md | ||
set-up-custom-end-user-email.md | ||
Simulate-slow-network.md | ||
Testing-and-local-development.md | ||
Troubleshooting-live-queries.md | ||
Vulnerability-processing.md | ||
windows-mdm-glossary-and-protocol.md |
Contributing
Building Fleet
Learn about building the code, development infrastructure, and database migrations.
Build and run Fleetd from local code
Building and running your modified code.
Testing
Look at Fleet's full test suite and integration tests.
Migrations
Learn about creating and updating database migrations.
Committing changes
Learn how to merge changes into the codebase.
Releasing Fleet
Learn the process for how to release Fleet.
Seeding data
Learn how to add fake data to your development instance.
API for contributors
Get to grips with Fleet API routes. This documentation is helpful for developing or contributing to Fleet.
Deploying ChromeOS test extensions
Learn how to deploy a test version of the fleetd Chrome extension for debug purposes.
FAQ
Find commonly asked questions and answers about contributing to Fleet as part of our community.