Hello,

 
Our ADSelfService Plus is configured to use SSL certificate.

 
To achieve that we enabled the HTTPS option under the Connection settings, and put the pkcs12 certificate in ADSelfService Plus that it is linked in server.xml like the following

 
<Connector name="SSL" sendReasonPhrase="true" relaxedQueryChars="\" port="443" minSpareThreads="25" maxThreads="150" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" connectionTimeout="20000" acceptCount="100" secure="true" scheme="https" keystoreType="PKCS12" keystorePass="XXXXXX" keystoreFile="./conf/XXXXXX.pkcs12" debug="0" clientAuth="false" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA" SSLProtocols="TLSv1,TLSv1.1,TLSv1.2" SSLEnabled="true"/>

 
It is working like a charm until now we decided to migrate to Azure and we wanted to publish the tool in the Azure Public Application Gateway.

 
It does not work, the reason in that apparently the Azure AppGateway V2 for communication with the backend is HTTPS it is a requisite that it is send the complete certificate chain.  However ADSelfService Plus it is sending only the Server Certificate (CA root and CA intermediate are not included missing)

 
In other words we need that in the answers ADSelfService Plus along with the Server Certificate are included the complete certificate chain (CA root and CA intermediate).

 
Might this be a misconfiguration on our part of an advance feature that need to be configured?