When connecting to a JIRA with a self-signed certificate, SP breaks with errors like these in the console:
angular.js:14362 Possibly unhandled rejection: {"error":{"cause":{"code":"DEPTH_ZERO_SELF_SIGNED_CERT"},"error":{"code":"DEPTH_ZERO_SELF_SIGNED_CERT"},"message":"Error: self signed certificate","name":"RequestError","options":{"auth":{"pass":"REDACTED","user":"jturner"},"body":{"fields":["summary","description","timeestimate","timespent","status","attachment","comment","updated"],"jql":"resolution = Unresolved ORDER BY updatedDate DESC","maxResults":100},"followAllRedirects":true,"json":true,"method":"POST","rejectUnauthorized":true,"resolveWithFullResponse":false,"simple":true,"uri":"https://issues.redradishtech.com/rest/api/latest/search"}},"requestId":"69215dc3-c079-4183-b258-db68b62e9ecc"}
Even though the OS trusts the self-signed cert, NodeJS doesn't.
Ideally, SP would pop up a dialog saying "This certificate is untrusted - continue?". Next-best option would be to figure out new NodeJS's mechanism for allowing extra trusted certs (nodejs/node#9139).
When connecting to a JIRA with a self-signed certificate, SP breaks with errors like these in the console:
Even though the OS trusts the self-signed cert, NodeJS doesn't.
Ideally, SP would pop up a dialog saying "This certificate is untrusted - continue?". Next-best option would be to figure out new NodeJS's mechanism for allowing extra trusted certs (nodejs/node#9139).