mSecure Support
Passkey issue in WhatsApp
Hi,
Thank you for contacting us. The workaround you have is the only way this can work since mSecure is seeing the same last 4 digits so it is assuming it is meant for one record in mSecure. When mSecure sees the same username is being used, it assumes only one account can use this username/phone number, so it only applies changes to the record that matches the username/phone number that it sees being used on the website. If mSecure was able to see the full phone number on the website, this would then resolve the issue. I'm sorry, but there is not much we can do in this situation.
Hi Mark,
I appreciate your reply and agree that such a case may be uncommon and I have only encountered it in this one particular instance.
However, I have come across some articles that mention username obfuscation through masking may be increasingly encouraged to prevent security breaches, especially in enterprise situations. It may be just a matter of time before username/passkey pairs are required to resolve masked usernames.
It would be more forward looking if rather than stopping at the very first instance of a match, to continue the matching process, listing all matches found and then to allow the user to identify and select the relevant username himself. Perhaps something to consider in a future update.
Thank you for your response. We will take this feedback in consideration for future updates we do and we thank you for highlighting a website that could benefit from a change in how the browser extension currently works. Please let me know if you need further assistance in the future.
JSeow