10-27-2014 15:55
10-27-2014 15:55
An http subscription url was working fine responding in 204.
After modifying the subscriber notification url to use https it began reporting 'SSLException'
I can't seem to locate any information on what the problem may be.
SSL is terminated using haproxy and the oauth process seems to be happy using https through and through.
This seems to be isolated to the notfication calls.
Answered! Go to the Best Answer.
10-27-2014 16:07
10-27-2014 16:07
Hello,
We support TLS(v 1.0)/SSL protocol for the subscriber endpoints. Please, note that we are not supporting self-signed certificates. We support only HTTPS connections to port 443. TLS+SNI is not supported at this time. Note that TLS v. 1.1. and 1.2 are not supported at this point.
Please check that you code satisfy all these requirements.
10-27-2014 19:05
10-27-2014 19:05
Thank you!
SNI is definately in effect here.
I will rework things to match what is supported.
10-27-2014 16:07
10-27-2014 16:07
Hello,
We support TLS(v 1.0)/SSL protocol for the subscriber endpoints. Please, note that we are not supporting self-signed certificates. We support only HTTPS connections to port 443. TLS+SNI is not supported at this time. Note that TLS v. 1.1. and 1.2 are not supported at this point.
Please check that you code satisfy all these requirements.
10-27-2014 19:05
10-27-2014 19:05
Thank you!
SNI is definately in effect here.
I will rework things to match what is supported.