bitwarden_rs 1.19 has been released
-
https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.19.0
Updated the admin interface:
- Added diagnostic and debug information.
- Added option to sort users by date.
- Added ability to modify a user's type in an organization and to delete the whole organization.
- Added support for the Personal Ownership policy, which when enabled disables the use of the personal vault to non-admin users of an organization.
- Improved shutdown behavior on Docker images, now should handle SIGTERM better.
Basic experimental support for LDAP import using the official Directory Connector.
- Note that users can't be created by this tool, it only can add or remove them from an organization.
- Autoimported users join the organization with user level and they need to be confirmed by an admin or owner from the web vault. If SMTP is enabled, users will need to accept the email invitation beforehand.
- Important: enabling the checkbox "Overwrite existing organization users..." in the Directory Connector can cause already existing users from the organization to be removed when syncing if they aren't present in the LDAP server, while the official server differenciates between manually added and autoimported users, and won't delete the manually added ones. This only applies to the user level, and not to managers, admins or owners, and will probably be changed in the future to align with upstream.
Updated web vault to 2.18.1.
Docker images are now built with docker buildx, which results in correct platform metadata.
Added opencontainers.org labels to Docker images.
Synced global domains data with upstream -
https://github.com/dani-garcia/bitwarden_rs/releases/tag/1.19.0
Updated the admin interface:
- Added diagnostic and debug information.
- Added option to sort users by date.
- Added ability to modify a user's type in an organization and to delete the whole organization.
- Added support for the Personal Ownership policy, which when enabled disables the use of the personal vault to non-admin users of an organization.
- Improved shutdown behavior on Docker images, now should handle SIGTERM better.
Basic experimental support for LDAP import using the official Directory Connector.
- Note that users can't be created by this tool, it only can add or remove them from an organization.
- Autoimported users join the organization with user level and they need to be confirmed by an admin or owner from the web vault. If SMTP is enabled, users will need to accept the email invitation beforehand.
- Important: enabling the checkbox "Overwrite existing organization users..." in the Directory Connector can cause already existing users from the organization to be removed when syncing if they aren't present in the LDAP server, while the official server differenciates between manually added and autoimported users, and won't delete the manually added ones. This only applies to the user level, and not to managers, admins or owners, and will probably be changed in the future to align with upstream.
Updated web vault to 2.18.1.
Docker images are now built with docker buildx, which results in correct platform metadata.
Added opencontainers.org labels to Docker images.
Synced global domains data with upstream@necrevistonnezr I seem to remember a Tweet where they were introducing a succession management or emergency access system into it.
Not sure if anyone's looked into that but I think increasingly important in a digital age where value is locked away with encrypted access.
-
@necrevistonnezr I seem to remember a Tweet where they were introducing a succession management or emergency access system into it.
Not sure if anyone's looked into that but I think increasingly important in a digital age where value is locked away with encrypted access.
@marcusquinn said in bitwarden_rs 1.19 has been released:
@necrevistonnezr I seem to remember a Tweet where they were introducing a succession management or emergency access system into it.
Not sure if anyone's looked into that but I think increasingly important in a digital age where value is locked away with encrypted access.
You mean this?! https://bitwarden.com/help/article/emergency-access/
Establishing Emergency Access to a Vault is available for Premium users, including members of Paid Organizations (Families, Teams, or Enterprise), but anyone with a Bitwarden account can be designated as a trusted emergency contact (i.e. your trusted emergency contacts do not need to have Premium).
-
@marcusquinn said in bitwarden_rs 1.19 has been released:
@necrevistonnezr I seem to remember a Tweet where they were introducing a succession management or emergency access system into it.
Not sure if anyone's looked into that but I think increasingly important in a digital age where value is locked away with encrypted access.
You mean this?! https://bitwarden.com/help/article/emergency-access/
Establishing Emergency Access to a Vault is available for Premium users, including members of Paid Organizations (Families, Teams, or Enterprise), but anyone with a Bitwarden account can be designated as a trusted emergency contact (i.e. your trusted emergency contacts do not need to have Premium).
@necrevistonnezr did not know Bitwarden had this feature! I've been longing for it! However, the docs say how to access it but I'm not seeing it in my self hosted version - is this not available for self hosted?
-
@necrevistonnezr did not know Bitwarden had this feature! I've been longing for it! However, the docs say how to access it but I'm not seeing it in my self hosted version - is this not available for self hosted?
@thetomester13 said in bitwarden_rs 1.19 has been released:
is this not available for self hosted?
Generally yes, but you always have to remember that bitwarden_rs is a volunteer driven implementation of the official serverside api. So just because Bitwarden implements a feature it does not mean the same will be available in bitwarden_rs.
-
@thetomester13 said in bitwarden_rs 1.19 has been released:
is this not available for self hosted?
Generally yes, but you always have to remember that bitwarden_rs is a volunteer driven implementation of the official serverside api. So just because Bitwarden implements a feature it does not mean the same will be available in bitwarden_rs.
@fbartels yep, you're right, I see it listed in the Features Request META issue.
