How to tell a connection is self-signed or not - Noteworthy at Compose

Published

This is your weekly summary of Compose news for those changes and updates which can make your life easier. In this edition, self-signed or not self-signed, we show how to quickly tell if a connection string needs a self-signed certificate or not when you connect to Compose. And we also look at the past week's Compose Articles.

Self-signed or LE certificates

We often get asked how users can discriminate between database connections which use self-signed certificates provided by Compose and connections which use Let's Encrypt (or LE) certificates. The Compose UI has been updated to only show self-signed certificates when they are needed but for some thats not enough - for example, when they are automating connections through the API. So here's the golden rule for connections and certificates on Compose.

Compose Articles

This past week we took a look at the state of MongoDB and Go drivers and covered the news of the week:

That's it for this week's Noteworthy at Compose. Onwards to next week!


Read more articles about Compose databases - use our Curated Collections Guide for articles on each database type. If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at articles@compose.com. We're happy to hear from you.

Dj Walker-Morgan
Dj Walker-Morgan was Compose's resident Content Curator, and has been both a developer and writer since Apples came in II flavors and Commodores had Pets. Love this article? Head over to Dj Walker-Morgan’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.