Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 24 Packages Projects Releases Wiki Activity

Update endpoints that need to be exposed (#27798)

Browse Source 
Most Fleet users want Fleet Desktop > My device page to work. I think
let's document that as the best practice

---------

Co-authored-by: Robert Fairburn <8029478+rfairburn@users.noreply.github.com>
This commit is contained in:
Noah Talerman
2025-04-02 15:44:17 -05:00
committed by GitHub
co-authored by Robert Fairburn
parent fc3cd3b33f
commit 2a3e99ae47
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/what-api-endpoints-to-expose-to-the-public-internet.md
+1 -1
View File
@@ -11,7 +11,7 @@ If you would like to manage hosts that can travel outside your VPN or intranet,
## Using Fleet Desktop on remote devices
If you are using Fleet Desktop and want it to work on remote devices, the bare minimum API to expose is `/api/*/fleet/device/*/desktop`. This minimal endpoint will only provide the number of failing policies.
If you're using Fleet Desktop `/api/*/fleet/device/*/desktop` must be exposed in the API, and for the end user **Fleet Desktop > My device** page `/device/*` and `/assets/*` must be exposed.
For full Fleet Desktop and scripts functionality, `/api/fleet/orbit/*` and`/api/fleet/device/ping` must also be exposed.