nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Passkeys issue: can’t delete old passkeys

SWR

It appears there’s an issue with managing passkeys in the web interface. I am unable to delete existing passkeys. The issue is there when using the Firefox browser on my PC, and my iPad using Safari, so it’s not a browser issue. I have 3 of them in the dashboard at present. Can anyone confirm?

There’s also an issue with trying to add passkeys in the web interface. It throws the following error:

“Unable to create passkeyWe were unable to create your passkey. Please try again or create a passkey later.”

However, it is possible to add a new passkey from my device (an iPad).

I’d also like to suggest that FTUSA add a time stamp to each passkey as there’s no way to see when they were created, and thus know which ones can be deleted vs. kept.

Find more posts tagged with

Account

Comments

TaxMorgan

Hello SWR,

Since we don't have access to your account information in the community, we are not able to confirm whether you see the option to delete your passkeys or not. I would recommend contacting us directly from the support center in your account for assistance with this.

Using a private browsing session/incognito mode and/or deleting the cache and cookies from your web browser may also help.

We will forward your recommendation of time stamps for passkeys to our development team.

SWR

Thank you for the follow-up. I use private browsing session/incognito mode by default and cache and cookies are deleted each browsing session when I close the browser. To clarify your response, the option to delete passkeys is there for each passkey and a pop-up appears when it's clicked to confirm deletion or cancel; it simply does not do anything. There also appears to be error when trying to create a new passkey in the control panel, but it appears to work if done through the device's workflow. Since this occurs on different browsers, I think it's not specific to my account and instead a platform issue that should be easy to verify, if you wouldn't mind advising the dev team.

TaxMorgan

Hello again,

I have forwarded the information you shared to our team. I would also recommend that you contact us directly from the support center so that we can look further into the situation from there where we have access to your account information.