Subscription development requirement

[FujiNguyen]

I have two questions about subscription requirement for developer.  

1.  It states that the Sel-signed certificates are not supported.   During development, developer uses self-signed certificate.  Is there workaround to avoid buying certificate?

2.  Why TLS+SNI is not supported?  The Mircosof Azure supports TLS+SNI.

Below is reference to the https requirements.   

https://dev.fitbit.com/docs/subscriptions/

Using HTTPS

Fitbit supports Transport Layer Security protocol - TLSv1.2 for the subscriber endpoints. HTTPS connections must use port 443.

Note: TLS+SNI is not supported. Self-signed certificates and all versions of SSL are also not supported.

[JeremiahFitbit · Accepted solution]

---

FujiNguyen wrote:

1.  It states that the Sel-signed certificates are not supported.   During development, developer uses self-signed certificate.  Is there workaround to avoid buying certificate?

---

There are a few options:

• You could use the Let's Encrypt certifiate authority.
• You could obtain a wildcard certificate and give developers their own subdomains.
• You could use ngrok.

---

@FujiNguyen wrote:

2.  Why TLS+SNI is not supported?  The Mircosof Azure supports TLS+SNI.

---

SNI does not make a server any more or less secure. It only enables virtual hosting (hosting more than one hostname per IP address). Fitbit does not currently support TLS+SNI, so your server must either have a dedicated IP address or default to routing traffic to your hostname. Microsoft Azure supports non-SNI TLS, so you should use that option.

[FujiNguyen]

Thank you for the answers.  I will give it a try.