Occasional problems when logging into SecurityAssist-powered sites on Chrome only

I always use SecurityAssist to build my protected pages. I've had a recurring issue though, only on Chrome, when a user tries to login to a site and is definitely using the correct login details, but it keeps saying the user login details are invalid. After a lot of trial and error, I discovered that it's linked to the way that Chrome saves user passwords - i.e. when you're logged into Chrome itself and you can see your little avatar top right. You login into a website and Chrome asks you if you want to save your password. It seems that if a user has chosen to remember the password, then at some point they input an incorrect password or update the password on a website, Chrome then gets the correct and incorrect details confused and even if you do then enter the correct details, Chrome doesn't recognise them. If you login via a Guest or Incognito window, it'll let you login to the SecurityAssist site no problem.

The workaround I've found is going into the list of saved passwords on Chrome and deleting any for that site that are saved, correct or incorrect. This then forces the user to re-enter the details next time they login and hey presto, it's fixed. Not very user-friendly though!

I'm not sure if this is only an issue related to how SecurityAssist works on Chrome or if it's a general issue with any password-protected sites? Is it something anyone else has come across? I'm continually having to send instructions to my clients' users to tell them how to remove their password from Chrome.

Any advice or insights would be appreciated!

I haven't seen that happen before. If you send me a url to your login page and steps to reproduce I can see if I can reproduce the problem. I will probably need FTP access to fully debug and determine exactly what is going on to find a solution.

I don't think I could give you the steps to recreate it as it seems to be a system-level issue on the Chrome browser. It doesn't happen to everyone but I have a lot of users who report that they have the issue, and unfortunately most are not particularly computer-savvy so it's a big deal trying to explain how to fix it.

When I Googled it, I found a few threads on Google Forums such as this one: https://productforums.google.com/forum/#!topic/chrome/Cz06JxDZeK8, so I was just curious if anyone else who uses SA has experienced it. It's never happened to me on the likes of eBay but has happened on client sites I've built with SA.

I can't imagine it would particular to SA, since it just depends on submitting a standard form. Figuring out steps to reproduce is the key to fixing any problem like this. Without steps to reproduce you couldn't ever really tell if you fixed it with anything you tried. If you ever do figure out steps to reproduce, let me know and I might be able to follow the steps and figure out where it goes wrong.