Common User for multiple URLs

I’m sorry if this has been asked before, I’ve just switched from Passman 2 weeks ago and I really like how this project has progress.

My issue is that I have many many sites I use that a have the same authentication backend. So when my password changes it changes everywhere and I can’t seem to figure out how to link all these urls to a common username and password. I was trying to use the tags and folders but that doesn’t seem to work like I expected.

Are there any tips or documents I haven’t discovered? Or is this just not possible?

Thanks again

You can add additional urls as a custom field in the edit dialog. The browser extension will then also suggest the password for the domains from those fields.

Thanks I tried that. I’m not sure what I’m doing wrong but now the experiences is a little worse. :frowning:

Here’s a small example of what I’m experiencing although the Number of sites I have using the same user backend is far greater than illustrated.

All of my sites have a LDAP backend. I have NextCloud installed at https://example.com/nextcloud I have the following URLs

Site 1 - https://example.com/nextcloud - 3 Passwords saved. 2 usernames

  1. The Admin Account - unique password
  2. My User Account - Unique password
  3. Unique Master Password for the password app in nextcloud (no username)

Site 1a - https://example.com/stats Uses the same username and password as #2 above

Site 1b - https://example.com/wiki - Uses the same usernamed and password as #2 above

Site 2 - https://support.example.com - Uses the same username and password as #2 Above

Site 3 - https://monitor.example.com/monitor - 2 Accounts 2 Passwords

  1. Same as #2 Above
  2. Special Admin Account

The web browser extension seems to only recognize the website URL when it’s explicit with full path and when using Nextcloud. It seems to ONLY recognize the Master password.

Furthermore, every time there’s a session ID in the URL path. The Collector thinks it’s a new URL.

New Observation -

When I go to https://example.com it lists the passwords for:

  1. Master Password - It shouldn’t since the URL is
    https://example.com/nextcloud/index.php/apps/passwords But acceptable.
  2. My Personal account - As it should since the main URL is https://example.com
  3. My Admin Account - It shouldn’t since the URL is https://example.com/nextcloud
  4. My Admin Account for https://monitor.example.com/monitor - It shouldn’t because the URL is https://monitor.example.com

I’m guessing we have a bug in the search and need to anchor the search. It appears to be doing a search for anything that matches “example.com” as grabbed from the address bar.

In SQL terms, I think it should be doing:
SELECT from password WHERE url = “https://example.com
instead it seems to be doing a
SELECT FROM password WHERE url LIKE '%example.com%"
and other times it’s doing a
SELECT FROM password WHERE url LIKE “%example.com/foo/blah&1233445%

FYI, I just noticed several other people have filed this as a bug at:

Fixing my first problem (by adding links for common logins), seems to have uncovered uncovered this for me :slight_smile:

I think I fixed it and sent a pull request your way.

I couldn’t figure out how to make this work using custom fields either. I tried setting some custom fields like:
url1 = https://example1.com
url2 = https://example2.com
etc…

I was able to get multiple-URL matching by including multiple URLs in the main Website field, like this (using spaces as separators):
Website = https://example1.com https://example2.com

Another user I was discussing this with mentioned that he had to use semicolons as the separator. I used spaces. He’s on password app v2020.12.3 and I am on v2021.2.0. Using password chrome extension v2.1.1.

One downside to this is that the resulting URL link in the Password app concatenates each entry into a giant URL, encoding the separating spaces as “%20”. This makes the “open link” feature unusable. I’ll look into filing a bug for this, assuming this is the intended use-case for this feature.

EDIT: It looks like this is the wrong way to approach this. The key seems to be using custom fields with field-type set to “Link”. See this issue for the Password app:

The browser extension (version 2.0.0 and later) checks the website fields and all custom fields with the type “link” (or “website” in 2021.4 and later).

So here is how to add a extra urls in 2021.3.0 an prior:
custom url 2021.3.0

And here is how to add extra urls in 2021.4.0 and later:
custom url 2021.4+

Note: Currently (march 2021), the search in the app doesn’t look into custom fields. The search in the extension only includes url when the keyword url: or host: is used and requires an exact match.

1 Like