Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Notification Subscriptions using https result in SSLException

ANSWERED

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.

 

Screen Shot 2014-10-27 at 4.29.48 PM.png

 

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.

 

Best Answer
0 Votes
2 BEST ANSWERS

Accepted Solutions

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.

Ivan Bahdanau
Senior Software Developer at Fitbit

View best answer in original post

Best Answer
0 Votes

Thank you!  

 

SNI is definately in effect here.

I will rework things to match what is supported.

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

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.

Ivan Bahdanau
Senior Software Developer at Fitbit
Best Answer
0 Votes

Thank you!  

 

SNI is definately in effect here.

I will rework things to match what is supported.

Best Answer
0 Votes