Is there any way that URIs can be minimized? I know that the idea of a password manager is to have a different password for each piece of equipment, but there are certain elements that we have to keep with the same password and when I click on the “autofill and save” option I already have about 81 URIs and when I have to add a new one, it becomes a bit tedious to slide to the end just to click on the same option.
Or in the case that you cannot minimize the order, the save option should appear before the URIs.
I myself have one item with 27 URI’s in my work’s vault. The authentication to all those services is tied to our Active Directory; something like SSO.
The vault item where I store my AD credentials has all those URI’s so that I can use autofill with them.
Perhaps there is a better way to manage that, that’s the best way I came up with when I started using bitwarden at work.
When I have to change my AD password I just have to update this single item (well, a couple of them actually, because some services require the username and domain to be specified in a couple of different formats).
My use for these items is that I store several computers of one of my clients, which unfortunately (in this aspect I do not command) have the same password.
I know that a workarround would be to configure a wildcard like this. The problem is that if I set it for all the “general” networks of my client, I may have these entries for other clients, since some ips can be repeated.
For example, for my lab, that I usually use the same password and in the same network, I have it with the wildcard I mentioned.
@Klaush_61 Beyond just a simple wildcard, you can create more sophisticated regular expressions. Is there no pattern that the computers of the “same-password client” have in common, which is not present in the IP addresses for the other clients’ computers?
Why do you have 81 different URIs in one login item??!?!???