Azure App Proxy - Zammad

Technical assistance
1
  • Used Zammad version: 6.5.0-1744362684.c8a525b6.bookworm
  • Used Zammad installation type: source
  • Operating system: Debian 12
  • Browser + version: Chrome 136.0.7103.93

Expected behavior:

Azure App Proxy redirects to our internal Zammad System.
Login with Microsoft should work as if we connect to the local URL.

Actual behavior:

Login with Microsoft gives back this error:

image
image665Ă—115 9.11 KB

2

Could resolve the issue:
The Auth Token was invalid because the Azure App Proxy URL was not the same as our internal URL.

Changed the App Proxy URL and setup according DNS Records - redirect and login is now possible.
On my Windows Client everything is working as it should.
Somehow on my iPhone it shows “lost connection to server” - I can access everything but can’t create or edit tickets, just loading, no error.

1 Like
3

Zammad does allow one FQDN only.
Your error indicates one of the following:

  • you have no functional websocket connections (mandatory)
  • FQDN both of Zammad (setting) and what your client uses differs
4

Thanks - FQDN was surely the first Problem, which is resolved by changing the external URL to the same as the internal and according DNS Setup.
Websocket Connection is supported with Azure App Proxy and works fine on my notebook when I connect over our App Proxy.
Error lost connection to server only shows on iOS Devices (tested a few more) connected over the App Proxy.
Connections in our internal network have no problems on iOS Devices.