In Password Safe, the sofware we are substituting with Passbolt, a very important feature is that of password aliases. That means that an independent entry (the alias) will always have the same password as another entry (the base), even when this changes, while all other attributes are independent (name, URL, comment, etc.)
Hello Noel, the feature you are describing is not supported at the moment. Can you elaborate about the use case, e.g. explain why it’s important, or the kind of workflow you use it in?
Q5. Community support
People can vote for this idea to show traction:
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)
Hello Remy, In some cases the administrator password for some storage arrays is set by the Client to be the same in all the arrays, or in other cases the IPMI/iLO/iDRAC passwords are left as they were by default. In some cases, the root password or Domain Admin is the same for groups of related machines, and is changed with some regularity but in all of them at the same time.
As our group isn’t allowed to change these, we need to take note of them in our Password Safe, to be substituted by Passbolt, as they are, all the same. This is very well managed by aliases, as we take note of the string only once (very handy when it changes), but make individual entries for each array or computer, with its own IP.
I’d like to add my support for this feature request! This is a feature that can be really helpful when using the same login for multiple sub-domains or related domains, for example if you have a login for both amazon-com and smile-amazon-com, or multiple TLD with different country extensions. In my case specifically, we have multiple environments for the same websites that we’re developing (e.g. domain-com and dev-domain-com), which I think is a pretty common scenario for the kind of user that Passbolt would attract.
LastPass gets pretty close with a feature called equivalent domains, but it’s not a password-level setting and thus cannot be easily shared with other users.
Note: I’m using “-” instead of “.” in the domain/subdomain examples since I’m a new user and cannot post more than 2 links per post.
was there any progress on this topic?
I am facing the same issue. Our company onPrem admin accounts are synced to several cloud providers. So I would like to have the browser extension to suggest me the same credentials for different domains.
It would help, if there is an option to fill in multiple domains for one passbolt entry :-).
But maybe there is already an option that I did not recognize.
I’m not sure if my request falls under this one or not, but I’ll throw it out there.
Sometimes we have multiple URIs that use the same login credentials. The first example that comes to mind is for sites that use LDAP or SSO. If https://netbox.example.com and https://bookstack.example.com are both using the same backend authentication, then it would be very handy to be able to have alias records as described in this thread, or even just the ability to add multiple URIs to a single record (such as implemented by 1password). An alternate implementation that would satisfy a subset of use cases would be wildcard URIs, like “https://*.example.com”, or even flexible match detection, as implemented by bitwarden: