AWS Route53: Pass Route 53 Resolver DoH access token as URL path segment
Summary
Updates the macOS configuration profile example to place the access token as a path segment (/dns-query/token/<your-token>) instead of a query parameter, adds required Payload* keys, and documents replacing the token, identifiers, and UUIDs.
Security assessment
The change concerns handling of the Global Resolver access token credential and explains that macOS drops query parameters, which would silently prevent the token from reaching the resolver; it documents correct token delivery but does not describe a fixed vulnerability.
Evidence
+On macOS, pass the token as a path segment (`/dns-query/token/<your-token>`), not a query parameter. macOS strips query parameters from the DoH server URL, so the token never reaches Global Resolver.
Diff
diff --git a/Route53/latest/DeveloperGuide/gr-platform-configuration-examples.md b/Route53/latest/DeveloperGuide/gr-platform-configuration-examples.md index b8cf11d..f2ba914 100644 --- a//Route53/latest/DeveloperGuide/gr-platform-configuration-examples.md +++ b//Route53/latest/DeveloperGuide/gr-platform-configuration-examples.md @@ -63 +63 @@ Create a mobile configuration profile with the following structure: - <string>https://a1bc234567890a.route53globalresolver.global.on.aws/dns-query?token=<your-token></string> + <string>https://a1bc234567890a.route53globalresolver.global.on.aws/dns-query/token/your-token</string> @@ -66,0 +67,8 @@ Create a mobile configuration profile with the following structure: + <key>PayloadDisplayName</key> + <string>Global Resolver DoH</string> + <key>PayloadIdentifier</key> + <string>com.example.dnssettings</string> + <key>PayloadUUID</key> + <string>uuid-1</string> + <key>PayloadVersion</key> + <integer>1</integer> @@ -68,0 +77,10 @@ Create a mobile configuration profile with the following structure: + <key>PayloadType</key> + <string>Configuration</string> + <key>PayloadIdentifier</key> + <string>com.example.dnssettings.profile</string> + <key>PayloadUUID</key> + <string>uuid-2</string> + <key>PayloadVersion</key> + <integer>1</integer> + <key>PayloadDisplayName</key> + <string>Global Resolver DoH</string> @@ -72 +90,18 @@ Create a mobile configuration profile with the following structure: -Install the profile through System Settings > Device Management. +###### Note + +On macOS, pass the token as a path segment (`/dns-query/token/<your-token>`), not a query parameter. macOS strips query parameters from the DoH server URL, so the token never reaches Global Resolver. + +Replace the example values: + + * `a1bc234567890a.route53globalresolver.global.on.aws`: your Global Resolver's DNS name. + + * `3.3.3.3` and `3.3.3.4`: your Global Resolver's IPv4 addresses. For dual-stack resolvers, you can also list its IPv6 addresses. + + * `your-token`: your access token value, as returned by `GetAccessToken`. Don't use the token ID. + + * `com.example.dnssettings` and `com.example.dnssettings.profile`: reverse-DNS identifiers for the DNS payload and the profile. `uuid-1` and `uuid-2`: unique UUIDs for each (for example, generate them with `uuidgen`). + + + + +Install the profile manually on the device, or deploy it through your mobile device management (MDM) solution.