Any way to prevent passwords from auto-becoming logins with the addition of a username?

klepp0906

I like to keep my login items as things i can actually autofill and log in to. this leaves it by and very large to websites and things accessible through a browser.

I have a few nvidia shields set up around the house with an ip address assigned to each and a designated hostname in my hosts file so i dont have to remember the ip address when I need to access them through explorer. Ive kept the required passwords for access in 1password as a password category item since i began using 1password.

today i was attempting access on a pc i dont usually and realized i forgot what the username for the shield was when windows prompted me for the credentials over the network. I had to run downstairs to the unit to get it and would love for it to be saved in my ShieldTV password entry but that converts it to a log in and this is purely a local network device. no website to add etc etc so id prefer to not mix it in with everything else.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

PeterG_1P

Hi @klepp0906, interesting use case.

A couple points:

1. You're right: password items do auto-convert to become a login item when someone adds a username. You can imagine why this is: in many or most cases, someone who edits a password item by adding a username to it means to use it as a login, so that change behavior makes sense.

However, in your case you could prevent it from doing this by adding the username to a different field. For example, you could create a new text field in the item, enter a username, and select Save. This will result in the relevant data being associated with your item (so you don't have to run downstairs to the unit anymore) and also could be copy / pasted as usernames typically are. It also won't result in the item being coverted in a login. 👍

2. On the other hand, if you're mostly worried about the data auto-filling into browsers, you could still enter the username into the username field. This will result in the item being converted to a login, but it won't autofill into websites unless you specify a URL in the website field as well.

But ultimately if you're more interested in keeping things organizationally tidy, perhaps solution #1 might work better for you after all.

Let me know what you think - I'll be interested!