Activity for
-
dominikrauch modified a comment on discussion Open Discussion
I'm not using one entry for multiple logins, just for multiple URLs (domains) of the same (e.g., steampowered.com and steamcommunity.com simply use the same username/pw -> your steam account). Something else is my government ID which I use in multiple URLs to login to various government services. Or my stackexchange.com account which I use for stackoverflow, etc. The reference/duplicate is also a workaround I guess, would be much easier to have multiple URLs for me, cause I also immediately see which...
-
I'm not using one entry for multiple logins, just for multiple URLs (domains) of the same (e.g., steampowered.com and steamcommunity.com simply use the same username/pw -> your steam account). Something else is my government ID which I use in multiple URLs to login to various government services. The reference/duplicate is also a workaround I guess, would be much easier to have multiple URLs for me, cause I also immediately see which ones go together. Cheers, Dominik
-
I'm not using one entry for multiple logins, just for multiple pages of the same (e.g., steampowered.com and steamcommunity.com simply use the same username/pw -> your steam account). Something else is my government ID which I use in multiple URLs to login to various government services. The reference/duplicate is also a workaround I guess, would be much easier to have multiple URLs for me, cause I also immediately see which ones go together. Cheers, Dominik
-
@steelej: Sorry, I was not clear enough in my wording. I meant "entry". Each entry currently has a single URL associated with it. E.g., KeePassDX on Android allows you to specify a list of URLs so that the autoamtic target window match works for multiple URLs in my browser's window title (I have a browser extension to show the host part of the URL in the window title). @Paul: Thank you, that could indeed work, it's a bit cumbersome, because I want to have the entry associated semantically to multiple...
-
Don't know if I'm in the right place here for feature requests. It would be very nice to have the possibility to add multiple URLs to an account for autofill on multiple domains.
-
Is it somehow possible to save password generators in the keepass database file so I have the same generators on all devices? If not: I want to file a feature request for this :-) Best regards, D.R.
-
Immediately tested it -> my most used scenarios are all working - looks good already :-)
-
Looks great! Thanks for your quick actions! I'll give your plugin a try until the weekend and see if there are any problems with it. For testing purposes you could add another case that checks http/https cannot be intermixed, i.e., that http://example.com doesn't match https://example.com and vice versa.
-
If your non-mainstream browser does post the URL to the browser window, then [...] This would be almost what I'm looking for. I'm looking for the same behavior as the chromeIPass plugin, i.e., "match the URL in the title, regardless of whether it has www or not in it", unfortunately, this would be a bit harder to implement, I can see that that's a problem. BTW: chromeIPass is unfortunately no longer maintained nor is it any longer available in the Chrome Store - it should probably be removed from...
-
If your non-mainstream browser does post the URL to the browser window, then [...] This would be almost what I'm looking for. I'm looking for the same behavior as the chromeIPass plugin, i.e., "match the URL in the title, regardless of whether it has www or not in it", unfortunately, this would be a bit harder to implement, I can see that that's a problem. BTW: chromeIPass is unfortunately no longer maintained nor is it any longer available in the Chrome Store - it should probably be removed from...
-
Appendix: you still have to disable "#omnibox-ui-hide-steady-state-url-trivial-subdomains" in Brave browser to make that patch work! Can't work otherwise!
-
Thank you, that brought me one step closer. Now if the URL field says "somepage.com" in KeePass it works. However, when I want to enforce the credentials being used only for HTTPS pages (i.e., when filling in "https://somepage.com" in the KeePass URL field, it does not work. I even tried setting the #omnibox-ui-hide-steady-state-url-trivial-subdomains flag to Disabled in Brave, so that the full URL including HTTPS is displayed in the browser. However, this didn't work for WebAutoType yet. Any ideas?...
-
BTW: if you have time switch from SF to GitHub, it makes contributing so much easier : D
-
Here is a patch file, I tried to stay "in bounds" of your solution style. Unfortunately you don't have any unit tests I could extend, so I only tested it manually. "Works on my machine with my kee pass" :-)
-
I don't really want to edit the auto type sequence of 250+ entries. Would you accept a pull request to add this feature? It could be an option called "Match sub domains as well".
-
https://somesite.onmicrosoft.com should not match against an entry for https://othersite.onmicrosoft.com Yep, that's right. But https://somesite.onmicrosoft.com should match https://sub.somesite.onmicrosoft.com - just like the default cookie policy. That's also what KeePassHttp implemented. It could be a valuable option for people like me. I don't want to enter a wildcard because this would not only match sub-sub domains but other sub domains as well. Which indeed is a security risk. Also a double...
-
Ah, I found the problem. The URL matching in WebAutoType does not work like the KeePassHttp matching. "https://www.somepage.com" does not match the KeePass entry "https://somepage.com" - is there any chance to get this in WebAutoType? Edit: With "to get this" I mean to match a more general URL if the more specific URL does not match any entry.
-
Ah, I found the problem. The URL matching in WebAutoType does not work like the KeePassHttp matching. "https://www.somepage.com" does not match the KeePass entry "https://somepage.com" - is there any chance to get this in WebAutoType?
-
Thank you, that brought me one step closer. Now if the URL field says "somepage.com" in KeePass it works. However, when I want to enforce the credentials being used only for HTTPS pages (i.e., when filling in "https://somepage.com" in the KeePass URL field, it does not work. I even tried setting the #omnibox-ui-hide-steady-state-url-scheme flag in Brave, so that the full URL including HTTPS is displayed in the browser. However, this didn't work for WebAutoType yet. Any ideas? Best regards, Domin...
-
Hmm, it looks like Brave is using the same window class as Chrome. Maybe it should work out of the box already? Do I need to add some special line of code to support a new browser? (I have "Use the URL field value for matching" enabled, so it should work with my setup...)
-
Hmm, it looks like Brave is using the same window class as Chrome. Maybe it should work out of the box already? Do you match the URL field or the Title field in KeePass with the URL in the browser?
-
(uisng KeePass 2.x, Windows 10)
-
Support for matching a window's title with the URL field in KeePass
-
Support for other Chromium-based browsers
1
