What determines Passport.js TLS certificate validation behavior when DNS resolution maps the authorization server hostname to an IP?
What determines Passport.js TLS certificate validation behavior when DNS resolution maps the authorization server hostname to an IP? Passport.js OAuth2 strategies rely on Node's https module for TLS certificate validation, and the default rejectUnauthorized option controls whether the module rejects certificates that do not match the presented hostname. When
passport