Scope the policy Authorization header to the manifest host - #13
Merged
Conversation
The CSP-delivered AuthorizationHeader authenticates against the manifest
server, but it was attached to every HTTP request. Azure blob storage
returns 403 Forbidden for public-blob requests carrying an Authorization
header it cannot validate, so any device with the policy failed every
package download instantly ("Download failed: Forbidden", DFS-CAD-03
2026-07-21) - and the org token leaked to whatever hosts package URLs
point at.
Record the host of the manifest URL actually used this run and attach the
header only to requests for that host. Cross-host downloads (the blob
endpoint) now go out clean, matching what a browser sends. Also give the
package download client the same BootstrapMate/<version> User-Agent the
manifest client already sends.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause of DFS-CAD-03's fleet-blocking 'Download failed: Forbidden': the CSP AuthorizationHeader (Bearer token in HKLM\SOFTWARE\Policies\BootstrapMate) was attached to every request, and Azure blob storage 403s public blobs on foreign Authorization headers. Verified on-box via remote registry read; browser (no header) downloads the same blob fine. Header is now scoped to the manifest host only - also stops leaking the org token to third-party hosts - and the package client gains the standard User-Agent.