Hi Arron,
Thank you for your quick response.
Regarding the proxy part: my IDP is LemonLDAP::NG, which serves as both my IDP and my Nginx reverse proxy. Since it is open-source and a versatile tool, it allows me to monitor all traffic through the logs. I have made some progress and have some specific information to share with you:
From the logs: https://connect.<mydomain.fr>/oauth2/authorize?response_type=code&scope=openid%20profile%20email&client_id=OpenIDMdaemon&state=07596abaca431d8cd18b7007a2846e85&nonce=103deca5c478401d4353ff18d77ba4d6&response_mode=form_post&redirect_uri=https%3A%2F%2Fmail.<mydomain.fr>%2FWorldClient.dll%3FView%3DOIDC
As you can see, the redirect_uri is indeed pointing to mail.<mydomain.fr>. Consequently, I cannot use https://webmail.<mydomain.fr>/WorldClient.dll?View=OIDC as you suggested.
In the MDaemon configuration, this field is greyed out, so I am currently stuck.
My other option would have been to publish the webmail behind the mail.<mydomain.fr> URL instead of webmail.<mydomain.fr>, but unfortunately, that is not possible. For security reasons, our architecture requires SMTP (mail.<mydomain.fr) and HTTPS (webmail.<mydomain.fr>) traffic to pass through two different public IP addresses.
The solution would be to either "un-grey" this field so I can specify it manually, or to modify this value directly in an MDaemon configuration file, rather than having it automatically generated as https://<SMTP Host Name>/WorldClient.dll?View=OIDC.
What are your thoughts on this?