#6334 Corporate netsec software on Windows may causes 'self signed certificate' verification errors Issue created by aaronsteers It appears that this happens as network packets are inspected and re-signed by software running in the background on the machine. In theory there should be a way to let users trust the certs issued by their corp IT teams, and/or selectively disable/mute validations from specific domains. Two instances so far reported in slack: • https://meltano.slack.com/archives/C01TCRBBJD7/p1656621387384619 • https://meltano.slack.com/archives/C01TCRBBJD7/p1656516344303779 --- Maybe (or maybe not) related: I went digging around we did have some historic references to 'self signed certificates' in

tap-gitlab

and in the SDK. In those cases, a suggested improvement was to leverage a python session object when preparing or making the request. • The applied change in the SDK was to prepare the request from the session object: https://gitlab.com/meltano/sdk/-/merge_requests/45/diffs •

merge_environment_settings

was noted in the historic

tap-gitlab

issue here as being relevant and skipped in certain codepaths: https://github.com/psf/requests/blob/8c211a96cdbe9fe320d63d9e1ae15c5c07e179f8/requests/sessions.py#L701 --- See below for guidance from Greg Vaslo on slack. Also this issue is noted as related (affects SDK taps but not Meltano core): • meltano/sdk#633 meltano/meltano