Navigating to https://uat.cheque-manufacturing.services.dh.com/shell01 results in the following error: DNS_PROBE_FINISHED_NXDOMAIN: uat.cheque-manufacturing.services.dh.com’s server IP address could not be found.  The CORB-blocked resource (https://fs.corp.dh.com/adfs/oauth2/authorize/...) hits a similar problem.

Question: Does the problem persist after disabling CORB by launching Chrome with the following cmdline flags?: --disable-features=CrossSiteDocumentBlockingAlways,CrossSiteDocumentBlockingIfIsolating

Question: Can you please look in the DevTools Network panel to check the http response headers of the blocked response?  This will help verify why the response is blocked.

Question: Does the problem persist after disabling CORB by launching
Chrome with the following cmdline flags?: --disable-features=
CrossSiteDocumentBlockingAlways,CrossSiteDocumentBlockingIfIsolating
The problem disappear after disabling CORB.

Question: Can you please look in the DevTools Network panel to check the
http response headers of the blocked response? This will help verify why
the response is blocked.
I'll let you know next Monday, because my colleague is going off work now.
Do you need the response before I disable CORB or after I disable CORB?

Regards,
Yong Wu

The same http response should be reported in DevTools with and without CORB, so either way should work.  Probably capturing it with CORB enabled makes it easier to double-check that the right response has been captured (by comparing the URL reported in the Network panel and in the CORB error message).

As per comment#2 adding label Needs-Feedback and requesting reporter to respond back on the info about http response headers of the blocked response in DevTools Network panel i.e., Comment#1(...Comment#3).

Thanks!