Hi,
my reverse proxy redirects SSL to http://ip.
everything went fine, but the callback URL in Zammad for 365 ist also http:/xyz and we need to migrate to 365.
Do I need to run Zammad itself in https mode to get an https:// callback uri?
How can i get it to work without Zammad itself having correct ssl certificates, because of the nginx reverse proxy?
Zammads FQDN is part of the callback URL you’ll receive. That also applies for the http type.
(see: Base — Zammad documentation )
Microsoft expects HTTPs URLs - you have no other choice but make your Zammad work via https.
It technically doesn’t matter if your certificate is public valid (at least not to Microsoft). Microsoft also doesn’t have to call your instance directly - your client does.
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.