Recherches récentes
Pas de recherche récente

Simon Pledger
Adhésion le 19 janv. 2024
·
Dernière activité le 19 janv. 2024
Suivis
0
Abonnés
0
Activité totale
3
Votes
0
Abonnement
1
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Simon Pledger
Simon Pledger a ajouté un commentaire,
Hi Peter
Thanks for your helpful reply and advice. I'll certainly explore Let's Encrypt going forward.
In the mean time I have actually managed to workaround the problem by opening an additional non secure http port on my same webapplication server and changing my webhook to call the http version of the endpoint instead. Zendesk isn't too happy about me using an http endpoint in my webhook and puts a warning under the field :-) ... but it does now work, and circumvents the ssl validation issue for my local testing.
Best regards
Simon
Afficher le commentaire · Publication le 19 janv. 2024 · Simon Pledger
0
Abonnés
0
Votes
0
Commentaire
Simon Pledger a ajouté un commentaire,
Hi everyone
I wish to have a webhook call an SSL endpoint on my local development machine, whose target webapplication uses a self signed certificate.
The webhook fails and the activity page reports " x509: certificate signed by unknown authority".
Is there a way to configure Zendesk to allow webhooks to call SSL endpoints with self signed certificates.
In contrast, URL Targets work fine and I have never had issues with them calling self signed certificate SSL endpoints. So I am a little puzzled why this restriction only seems to exist on webhooks. It is sadly preventing me from doing any local development and prototyping at the moment
Thanks in advance for any help
Simon
Afficher le commentaire · Publication le 19 janv. 2024 · Simon Pledger
0
Abonnés
0
Votes
0
Commentaire