v0.11.0
Welcome to the next release on the road to v1.0.0. I added some requested features and quality of life changes to this version. Furthermore a good mix of bug fixes and dependency updates.
New Features
- Add granularity to validity: Before the validity of certificates and CAs could only be chosen in years. Now there is a huge span of units all the way from hours to years. Thanks for the request @Mr-win7. 1c2fb50
- Add OU field to X509 certificates: As requested @samphonic I added the OU name field to the TLS certificate creation that can be used for example to specify group memberships of a user. bf7bc51)
QoL
- Add retry for OIDC discovery: Sometimes VaulTLS starts before the OIDC service becomes available. Now when a user tries to use OIDC based login, VaulTLS will retry discovery if it is configured but has not been successful so far. 625577b
- Improve frontend error message: The API already reports better error messages, but they have not been included in the displayed error message so far. Append the API error to the displayed message so you better know whats going on without looking into the console. ccc8879
Bugs
- Fix saving settings on frontend: When settings are saved, it puts data to two endpoints: settings and users. The users endpoint has been configured wrong leading to an error message when trying to save the settings. Adjust frontend users API interface to match backend. e85eea0
- Remove auto-renewal for CAs: When a user created a certificate without specifying a CA and the certificate would be valid for longer than the CA, VaulTLS would auto renew the CA in the hopes that then the CA would live long enough. While this was intended behavior, in hindsight this approach is too in transparent. Creating CAs without the users active knowledge is probably not desireable so I removed this ¨feature¨. c62045f
Dependency updates
- Lots of dependencies were updates
I appreciate all your support! Thank you so much :)
Full Changelog: v0.10.0...v0.11.0