You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run slack locally and the address is https but our certs are self signed. I can send a insecure http webhook to a python connector that then forwareds it along to Slack but doesn't verify our self signed certs. When I send the webhook directly to our https slack implementation it fails. I think that I can't send a slack webhook because in the background the slack endpoint wants to verify the certificate and it can't because it's self signed.
In telegraph it looks like you can set "insecure_skip_verify = true" and it will ignore a self signed certificate.
Could this possibly be implemented in the Slack and other notification endpoints?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We run slack locally and the address is https but our certs are self signed. I can send a insecure http webhook to a python connector that then forwareds it along to Slack but doesn't verify our self signed certs. When I send the webhook directly to our https slack implementation it fails. I think that I can't send a slack webhook because in the background the slack endpoint wants to verify the certificate and it can't because it's self signed.
In telegraph it looks like you can set "insecure_skip_verify = true" and it will ignore a self signed certificate.
Could this possibly be implemented in the Slack and other notification endpoints?
Beta Was this translation helpful? Give feedback.
All reactions