Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content

Vault

4 Topics 109 Posts
  • Vault - Package Updates

    Pinned
    91
    0 Votes
    91 Posts
    34k Views
    Package UpdatesP
    [1.82.0] Update vault to 1.21.0 Full Changelog auth/ldap: fix MFA/TOTP enforcement bypass when username_as_alias is enabled. activity: Renamed timestamp in export API response to token_creation_time. http: Add JSON configurable limits to HTTP handling for JSON payloads: max_json_depth, max_json_string_value_length, max_json_object_entry_count, max_json_array_element_count. AES-CBC in Transit (Enterprise): Add support for encryption and decryption with AES-CBC in the Transit Secrets Engine. KV v2 Version Attribution: Vault now includes attribution metadata for versioned KV secrets. This allows lookup of attribution information for each version of KV v2 secrets from CLI and API. Login MFA TOTP Self-Enrollment (Enterprise): Simplify creation of login MFA TOTP credentials for users, allowing them to self-enroll MFA TOTP using a QR code (TOTP secret) generated during login. The new functionality is configurable on the TOTP login MFA method configuration screen and via the enable_self_enrollment parameter in the API. activity (enterprise): Fix development_cluster setting being overwritten on performance secondaries upon cluster reload. auth/cert: Recover from partially populated caches of trusted certificates if one or more certificates fails to load. auth/spiffe: Address an issue updating a role with overlapping workload_id_pattern values it previously contained. core: Role based quotas now work for cert auth
  • Vault - OIDC Support

    5
    0 Votes
    5 Posts
    919 Views
    C
    @joseph I agree. I looked at some of the implementation requirements and it takes effort. With each Cloudron app update and server reboot, it requires a process to "turn on" the server. That involves presenting several keys to unlock the server. For large companies with dev ops resources, this is doable. But for smaller companies, it is too much effort with a huge risk of bringing down applications if you miss a secrets server reboot.
  • Vaultwarden vs Vault

    8
    1 Votes
    8 Posts
    5k Views
    marcusquinnM
    @scooke Think of Vault as kinda like Bitwarden but for code to lookup with. Unless you're coding access to things, I don't think you'd need it.
  • Vault process running out of memory--plenty of memory available.

    Moved oom
    5
    0 Votes
    5 Posts
    2k Views
    girishG
    @mastadamus I will bump up the memory limit for vault. https://learn.hashicorp.com/tutorials/vault/reference-architecture says 4-8GB is recommended. Currently, the cloudron package runs at 256MB! Also, as you guessed, it's only the vault container that is dying and the server is not affected (I guess that's one of the main benefits of running in containers, a single app cannot bring down a system).