Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix CRD remote command when RemoteAccessHostDomainList is set
The CRD Remote Command uses a very specific, internal host domain (chrome-enterprise-devices.gserviceaccount.com) to establish the connection. If the customer uses the RemoteAccessHostDomainList policy this will cause the CRD Remote Command to be rejected, unless the customer adds this internal host domain to their allowlist. This CL fixes this by skipping the host domain check for the CRD Remote Command enterprise connections. (cherry picked from commit 9d3fc53) Fixed: b/227767159 Test: new unittest in remoting_unittests Test: manually deployed Change-Id: I21952f132ce0b6a49fdb8012ab6cbb174007052e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3649602 Reviewed-by: Joe Downing <joedow@chromium.org> Auto-Submit: Jeroen Dhollander <jeroendh@google.com> Commit-Queue: Jeroen Dhollander <jeroendh@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1004293} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3663223 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5060@{#398} Cr-Branched-From: b83393d-refs/heads/main@{#1002911}
- Loading branch information