Browser integration: multiple URLs

[Thulium-Drake]

Expected Behavior

Allow for multiple specifications for URLs on which the use of a credential is allowed.

Current Behavior

You can only set 1 url (or wildcard) on a credential, even if the systems on those urls share a common authentication source (e.g. LDAP)

Possible Solution

I think the best implementation for this would be the same as how one would 'describe' Auto-Type sequences and windows, like so:

URL: https://auth.example.com
URL-1: https://auth.examplesotherdomain.com
URL-2: https://somehost (which would be in the local network's search domain)

(P.S. for those who might not know, https://*.example.com is a valid URL ;-), but that doesn't allow for mulitple domains or the single word DNS names)

Context

I'm trying to migrate from all auto-type to a more integrated solution and this is stopping me from doing so :-)

Debug Info

KeePassXC - Version 2.3.1
Revision: 2fcaeea

Libraries:

• Qt 5.7.1
• libgcrypt 1.7.6-beta

Operating system: Debian GNU/Linux 9 (stretch)
CPU architecture: x86_64
Kernel: linux 4.9.0-6-amd64

Enabled extensions:

• Auto-Type
• Browser Integration
• Legacy Browser Integration (KeePassHTTP)
• SSH Agent
• YubiKey

[varjolintu]

See this #1769. When it's merged I will do any necessary changes to the browser integration side.

[Thulium-Drake]

Thanks for the prompt reply! That does indeed seem to accomodate this usecase quite well!

[droidmonkey]

Edit: I see now that this is targeted for the browser plugin side.

[Thulium-Drake]

Hi Guys,

Thanks for integrating this feature! From what I can see in 2.3.4 this works like a charm!

[twwd]

How does it work? I can't find any details about that.

[droidmonkey]

This is an issue, not a code contribution. (and its closed, no work was done here)

[twwd]

I know that this is just an issue but @Thulium-Drake wrote:

Thanks for integrating this feature! From what I can see in 2.3.4 this works like a charm!

The method described in the linked PR #1769 doesn't work (the PR is closed anyways) and I couldn't find any information in the changelog of version 2.3.4. So I want to know how it works for @Thulium-Drake.

[Thulium-Drake]

@twwd

I have something like this:

https://login.example.com|https://login.otherexample.net 

Set as the URL for an entry and the browser plugin picks up on it.

[brainplot]

https://login.example.com|https://login.otherexample.net 

@Thulium-Drake Is that really how it's supposed to work or are you basically injecting regex syntax?

[Thulium-Drake]

This is how I'm using it at the moment, but I'm not sure what it will do underwater :-)

[AlexanderAmelkin]

I have something like this:
https://login.example.com|https://login.otherexample.net
Set as the URL for an entry and the browser plugin picks up on it.

This definitely does NOT work for me with KeepassXC 2.5.1 and KeepassXC-Browser 1.5.3.
The extension just can't find the record at all.

[varjolintu]

@AlexanderAmelkin That worked becase of an earlier bug. Anyone, do not use it.

[YogSottot]

This definitely does NOT work for me with KeepassXC 2.5.1

@AlexanderAmelkin You should use this #3558

[AlexanderAmelkin]

@YogSottot, thank you so much! It doesn't fully work for me as expected (described there), but it solves the problem.

[fourstepper]

Is there a way to use regex with the URLs?

[varjolintu]

@fourstepper At this point, no.

[fourstepper]

thanks for the swift reply - that's not a big deal

[JohnLGalt]

You want a comment from over 2 years ago to be edited now, after the feature has been properly implemented into KPXC?

[Jorricks]

Alright alright. Maybe that is expecting a bit to much 😅 it's just that I was trying that method and couldn't get it to work. Guess I should have scrolled down.