Q1. What is the problem that you are trying to solve?
Currently passbolt only allow to stores passwords. It should allow administrator to create more complex types. For example let’s say I want to add the pin number to a site say this type of entry is for a “pin” with name and secret of type scalar.
Q2 - Who is impacted?
Administrators with authentication requirements that goes beyond passwords.
Q3 - Why is it important and/or urgent?
Passbolt should be flexible and not force a format for a given secret, considering that they are multiple ways to authenticate against other systems and not just passwords.
Q4 - What is your proposed solution? (optional)
The idea would be to allow admin to create any secret format by adding/removing the metadata (field name and types and validation rules). Passbolt will then present a workspace for each types to the end user as well as create / edit form based on the metadata. We will provide a few base types by default such as passwords (url, login, password), credit card (owner, card number, etc.), notes (textarea), and let admin create their own.
Good idea, sometimes a password entry can have more than one password for one log-in site (so it must have one entry but has more than one password; say main password for a (sub-)organisation and one sub-passwort for a specific user).
This would have the added benefit of also addressing the secure notes request. All admin needs to do is create a new secret textarea field and voila, secret notes! Two birds with one stone!
does anyone know if this feature has been discussed in the development team? I think that would be a great improvement as we now mainly use password-less keys to connect to our servers.
Yes we have been actually actively developing a proposal for an open standard and a prototype for this feature in partnership with the fine people Mailvelope and Gnupg (peer reviewed by Cure53) that will allow anybody to define and capture data encrypted end to end using a new HTML component called “encrypted forms”. We’re still a long way to go before it’s included in Passbolt but a prototype will be available for Mailvelope in September or so.
Use case is: storing certificates in encrypted containers. It is useful to store a certificate not as a text, but as encrypted container file, like P12. Containers are handled consistently on given OS, so are user-friendly. Container is physically a binary file. So I woud like to store secret which is a password and a binary file, that is the certificate within container.
I need a way to add custom fields such as external ip, external nat port, etc… would be great if we can add a few custom fields and select the data type (Numeric, char, true/false, etc…)
hey. i want to switch to passbolt, but this one is a bummer…
for switching to passbolt, i need this feature.
because what should i do with my credit-card infos, photographed documents etc ? leave it in bitwarden? so i have two password-managers? no i have to wait then…
Must have: this is critical for me to have this
Should have: this is important for me to have this
Could have: this could be nice to have
Won’t have: we should not schedule this (explain why)
i have to wait then…