ConfigSeeder 2.17 with improved certificate management

Just in time for Christmas ConfigSeeder Release 2.17.0 was published for you. There are exciting changes, especially for certificate management.

Daniel Kellenberger

4 mins read

Download ConfigSeeder® Management 2.17.0

Download

Download ConfigSeeder® Kubernetes Connector 1.3.4

Download

Download ConfigSeeder® OS Connector 1.1.4

Download

Download ConfigSeeder® Lookup Plugin for Ansible 1.0.0

Download

Highlight Features

Certificate Management: Keystore Preview

With this release, it is even easier to verify how the keystore (PKCS12/JKS) is assembled. Regardless of whether the various certificates are outsourced to a separate configuration group or contained within the assembly, the preview shows the certificates and the private key.

ConfigSeeder Certificate Management
A tree based preview shows all certificates and private keys contained in the keystore

Certificate Management: Notification if a certificate is nearing the end of its lifetime 

Unfortunately, this still happens too often nowadays: certificates expire without this being detected in time, resulting in the inability to establish a connection. ConfigSeeder® notifies in time when stored certificates are about to expire and need to be replaced. For more details check our Configuration Documentation.

Lookup Plugin for Ansible has reached 1.0.0

Easily retrieve configuration data used by Ansible Playbooks from ConfigSeeder. Compared with storing configuration data directly in ansible, using the ConfigSeeder Ansible Lookup Plugin has the following advantages:

  • While Ansible Vault is a secure way to store secrets directly in the ansible files, it is quite cumbersome to work with it. The values must be manually encrypted (and decrypted if an encrypted value has to be verified) and the key for the vault must be distributed manually if multiple administrators need to work with the key. Secrets retrieved from ConfigSeeder® are also stored encrypted, but can easily be managed using the Web UI.
  • Configuration data stored in the ansible files can only be used by Ansible playbooks. Configuration data stored in ConfigSeeder® can also be used for other purposes (access with clients, Kubernetes Connector, and/or OS Connector).
  • To see what configuration values are used by ansible, one normally has to look into the source control system storing the Ansible files. With ConfigSeeder®, the configuration data can easily be accessed with the Web UI.

For more details check our feature description about Ansible integration.

All Changes (ConfigSeeder® Management)

Please check the list of breaking changes. For more details please visit https://download.configseeder.com/management/CHANGELOG.md

Added

  • Certificate Management: Show Information for private keys #930
  • Certificate Management: Allow downloading the Keystore #1195
  • Certificate Management: Send notification if a Certificate is nearing the end of its lifetime #1098
  • Configuration Values: Filter and Highlight ConfigurationValues #1238
  • Docker: Add OpenSSL to docker image #1282

Improved

  • Configuration Value Restore: Improve validation of “restore value dialog” inputs #1198
  • Statistics Calling Clients: Colorize and name clients #1221
  • User management: Improve selecting permissions for function role #1228

Fixed

  • Template Preview: content overflowing #1206
  • UX: Multiline String Popup closes when pasting content #1207
  • Assembly: Grid resizing issues #1210
  • UX Assembly: Unable to leave assembly view with browser back #1213
  • Preview Dialog: Scrollbar at the wrong place #1237
  • Assembly Detail: Assembly content not fully visible #1260
  • Configuration Groups: Layout broken #1268
  • Configuration Value: Warning column missing space #1269
  • Configuration Value Restore: Broken restore dialog for assemblies without attributes #1275
  • API Key: Renew not possible when only the validity field has changed #1276