Wht's this Conflicts ... trusted ... on login entry?

Petra

Hi guys,
I'm on Mac OSX 10.10.5 with 1PW 5.3 MAS.
I have one (primary) vault that syncs with iCloud.

I was renewing passwords for this email account when something came to my attention, please see the attachtment, circled in red, I see Conflicts, trusted, 4
What does it mean??
I searched the help and the forum, to no avail.
Could you please tell me what it is and how to deal with this?

BTW, there are no vulnerable items in my watchtower.

Thanks.

removed by AgileBits

---

1Password Version: 5.3
Extension Version: 4.4.4
OS Version: OSX 10.10.5
Sync Type: iCloud

littlebobbytables

Hi @Petra,

So a conflicts section occurs when 1Password is trying to merge changes between it's locally stored vault and the external sync container but it finds that something seems to have been changed in both locations. When 1Password can't reliably say which is correct it will create a Conflicts section and store on version there while the other remains in the correct place. Basically we rely on the user knowing which is good and which isn't.

Now that field label instantly makes me think that it came from the web form details section of the Login item. That section is a record of the actual page that the Login item needs to work on (in terms of the fillable fields). I would say that in this instance you're quite safe to remove it without any adverse effect.

Hopefully that eases any concern you might have but if not please do let us know and we can discuss it in more detail if you wish. I hope you don't mind but I removed the image you kindly posted. It helped highlight the problem but I don't know if you really want your username visible in our forums which are openly accessible.

Petra

Thanks. Quite right to remove my posted image, not that anybody could easily guess my 1PW generated password, but better be on the safe side.
I'm not sure I really get what you're saying, as I don't see a Conflicts section in 1PW.
Just the Conflicts label with some of my Items.
They are the same on iPhone and iPad ... (of course they are, they're synced)
So really what you're saying is the conflict is with the fillable fields not being present, or different or what?
Let's just say I don't understand what the conflict is about, I know I can dlete/remove with edit, but I would like to understand the issue first.

littlebobbytables

Hi @Petra,

So you see how the word Conflicts is in bold and appears over the value rather than the field label? The word Conflicts is the title for a custom section and each row in the section will represent an individual conflict that has been recorded. So when I said conflicts section I could have been more accurate and said a custom section with title Conflicts.

It's unusual to see a conflict arise from a web form entry but it is most likely harmless. I personally haven't explored this area as much as maybe I should have but if memory serves me correctly it could be from either a modification or deletion. The key part is that an item have changed in two locations before one could inform the other. Normally what happens is 1Password knows you haven't edited an item, say on your Mac but sees a new version is in the sync data. It uses the new one as it knows you were in sync before but this newer version is now available. Depending on internet connectivity, service availability and timings though it can happen where 1Password on your Mac knows it has edits it needs to upload to your sync container but then it gets informed there is a new version too. All it can do is compare the two items, notice all differences and store those differences. It might be from both additions/deletions as well as modifications. I don't know the code though so I can't say "it will behave exactly like this" and then list an algorithm which would be great for those interested in the details.

Given the entry is almost guaranteed to have come from the web form details section the easiest thing to do is to try logging in with the Login item. If it works it may very well be a field that wasn't actively involved in the authentication process as you'd be amazed at how many fields a login page contains that probably aren't involved. If the Login item works you're free to delete :smile:

Does that help at all?