Autofill behaviour: Exclude subdomains
Comments
-
I have a similar feature request based on the workaround I use for a situation similar to yours. On my AD domain, let's say example.local, some logins need example\username but others will fail unless it's only username. My workaround has been to use the website autofill behavior custom settings to specify where to use certain sets of credentials. Obviously the drawback is that you need to create multiple entries for the same set of creds.
Anyway, the feature request I have to to adjust the website autofill custom options to include a "use on this domain and all subdomains EXCEPT for X, Y, and Z subdomains." That would help.
0 -
Hello @dmveron! 👋
Thank you for the feedback! Can you tell me a little more about your feature request? At the moment you can find the available autofill behaviour listed here: Change where a login is suggested and filled
You wrote:
Anyway, the feature request I have to to adjust the website autofill custom options to include a "use on this domain and all subdomains EXCEPT for X, Y, and Z subdomains."
Wouldn't you still need to create multiple login items even with this system? One login item for each "collection" of domains/subdomains that uses a particular login?
At the moment the best way to store AD logins is to have a single login item with multiple website URLs or sections. Then, if your AD solution doesn't support the exact same username across services, you could autofill the password and then copy and paste, or drag and drop, the username. Is that a workflow that might work better for you?
I look forward to hearing from you so that I can pass your feedback/request along to the team. 🙂
-Dave
0 -
+1 for the general ability to specify auto-fill behaviour by exclusion in addition to inclusion, together with sub-domain wildcards.
0
