KeePass User

OK, thanks, Dominik. As it does actually work, if the USERNAME field is not a reference, or if the URL field does not end with a USERNAME reference, I thought this was acceptable. Understood, if it is unsupported behaviour. Thanks for clarifying.

Hi, Paul. well, yes, I can workaround the problem - as mentioned in my second post, I can also replace the referenced username in the entry to be the actual username and that will also fix the output, but I think I'm fairly confident now that this is a bug and this behaviour should be expected to work. I raised it here first as, when I first started this thread, I wasn't sure if I was dealing with a bug or if I was misusing some KeePass functionality. It sounds like you have reproduced it? If so,...

Sorry, perhaps I wasn't clear enough. The URL Override does not use T-REPLACE-RX, that function is only used once - in the URL field. The entry which does not correctly populate the USERNAME field consists of: Username: {REF:U@I:E69BBBFE3506084499222C07119C873A} (a reference to a username in another entry) Password: {REF:P@I:E69BBBFE3506084499222C07119C873A} (a reference to a password in another entry) URL: ssh://hostname.example.com:22/home/{T-REPLACE-RX:"{URL:HOST}"(^[^\.]+)(\.)(.*\..*)"$1_$3"}/{USERNAME}...

Sorry, perhaps I wasn't clear enough. The URL Override does not use T-REPLACE-RX, only once in the URL. The entry which does not correctly populate the USERNAME field consists of: Username: {REF:U@I:E69BBBFE3506084499222C07119C873A} (a reference to a username in another entry) Password: {REF:P@I:E69BBBFE3506084499222C07119C873A} (a reference to a password in another entry) URL: ssh://hostname.example.com:22/home/{T-REPLACE-RX:"{URL:HOST}"(^[^\.]+)(\.)(.*\..*)"$1_$3"}/{USERNAME} URL Override: cmd://cmd...

Hmm ... I've done some further experimentation. My entry contains a URL field of: ssh://hostname.example.com:22/home/{T-REPLACE-RX:"{URL:HOST}"(^[^\.]+)(\.)(.*\..*)"$1_$3"}/{USERNAME} I've extended the URL Override in my last post for this entry, which now includes the password and URL: cmd://cmd /c "echo Port: {URL:PORT} Dest: {USERNAME}@{URL:HOST} Password: {PASSWORD} {URL} & pause" This URL Override works correctly if the username is directly specified ... but it doesn't work if the username is...

Hi, I'm using KeePass 2.36 on Windows 10 Anniversary Edition and was wondering if someone could help me with a behaviour I'm seeing that I'm not expecting. If I set an entry's URL Override field to this: cmd://cmd /c "echo Port: {URL:PORT} Dest: {USERNAME}@{URL:HOST} & pause" I get what I expect to see ... a window with all the placeholders correctly populated. However, if I change the URL Override to be this: cmd://cmd /c "echo Port: {T-REPLACE-RX:!{URL:PORT}!80!!} Dest: {USERNAME}@{URL:HOST} &...

Hi, Paul. Yes, as I mentioned - I had looked at the Global Auto-Type hotkey, but it really didn't work very well for me at all. There are a tonne of different windows, applications etc. that I potentially need to use different passwords in. It very quickly became apparent that the maintenance required would take up more time than hunting for the appropriate password in the database each time. The HotKeyEnabled plugin is better for what I need - pasting the appropriate password, based on the hotkey...

Hi, I originally looked at the global auto-type hot key, but I don't think it works very well in my use case. Specifically, the main complex password I want to use is a functional account which I use with many different windows and tabs (often on the command line, rarely webpages), so the requirement that the entry title is part of the windows title rapidly becomes onerous.. The HotKeyEnabled plugin is closer to my use-case - having tried it at home, I could use it assign a different hot key to each...