GVL storage disclosure files failing to fetch

[dgirardi]

The following disclosure files are failing SSL validation:

- fetch failed for "bidder.adyoulike" (gvl id: 259, disclosureURL: "https://adyoulike.com/deviceStorageDisclosureURL.json"), error:  TypeError: fetch failed
     code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
     
- fetch failed for "bidder.e_volution" (gvl id: 957, disclosureURL: "https://e-volution.ai/file.json"), error: 
    code: 'CERT_HAS_EXPIRED'
    
- fetch failed for "bidder.screencore" (gvl id: 1473, disclosureURL: "https://screencore.io/tcf.json"), error:
    code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'

While these return an HTTP error:

- fetch failed for "bidder.blockthrough" (gvl id: 815, disclosureURL: "https://blockthrough.com/tcf_disclosures.json")
     status: 403,                                                                                 
     statusText: 'Forbidden',

- fetch failed for "userId.ceeId" (gvl id: 676, disclosureURL: "https://ssp.wp.pl/deviceStorage.json"), error:  Response {
  status: 449,
  statusText: '',
  
- fetch failed for "bidder.contentexchange" (gvl id: 864, disclosureURL: "https://hb.contentexchange.me/template/device_storage.json"), error:  Response {
  status: 403,
  statusText: 'Forbidden',

With the exception of e_volution, all of them work in a browser but not with the release automation. the UNABLE_TO_VERIFY_LEAF_SIGNATURE suggests a difference in the trusted CAs (quickly trying https://www.npmjs.com/package/ssl-root-cas did not work); the 4xx errors suggest server side bot detection.

[patmmccann]

let's email whatever we find in the corresponding md file on failure

[patmmccann]

plan is we will not remove the cert check and we will attempt to fix the leaf issue

[Templier]

fetch failed for "bidder.adyoulike" (gvl id: 259, disclosureURL: "https://adyoulike.com/deviceStorageDisclosureURL.json"), error: TypeError: fetch failed
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'

This is due to a missing intermediate in the certificate chain. We (AdYouLike) are working on updating the certs returned by our server, which should fix the validation.

Update (January 22): we now return a complete chain which should address the validation issue.