Passkeys created in Librewolf not recognized by Firefox

[debmint]

I've set up some passkeys using Librewolf. They work fine under Librewolf and Brave, but they don't work in Firefox. I just get a prompt to enable my device and it times out if I wait. I checked to make sure Passkeys are enable in Firefox, and they are. When I am on the login page, on Firefox and all the others the page says the browser has partial support for passkeys.

Would anyone have any idea what else I might look for to see why this is occurring?

[varjolintu]

Does about:config show any differences between webauthn and passkey settings when compared to Librewolf?

[ghost]

They are both 128.0 (Debian)

[debmint]

They are both 128.0 (Debian)

After a month letting it slide, I revisited the issue, and I found that Passkeys were not enabled in Firefox. I could have sworn I checked that at first!

Now it seems that If I try to log in to GitLAB, it pauses on prompt to touch device. If I cancel and retry, it works. I saw on discussion in maybe keepassxc-browser repo a few months ago that gitlab was not yet functional. One odd thing, GitLab passkeys are stored under "KeePassXC-Browser-Passwords", and GitHub passkeys are stored under "Imported Passkeys". I wonder what is the difference?

[varjolintu]

They are both 128.0 (Debian)

After a month letting it slide, I revisited the issue, and I found that Passkeys were not enabled in Firefox. I could have sworn I checked that at first!

Now it seems that If I try to log in to GitLAB, it pauses on prompt to touch device. If I cancel and retry, it works. I saw on discussion in maybe keepassxc-browser repo a few months ago that gitlab was not yet functional. One odd thing, GitLab passkeys are stored under "KeePassXC-Browser-Passwords", and GitHub passkeys are stored under "Imported Passkeys". I wonder what is the difference?

"Imported Passkeys" is used by default when importing passkeys.

[debmint]

After a month letting it slide, I revisited the issue, and I found that Passkeys were not enabled in Firefox. I could have sworn I checked that at first!
One odd thing, GitLab passkeys are stored under "KeePassXC-Browser-Passwords", and GitHub passkeys are stored under "Imported Passkeys". I wonder what is the difference?

"Imported Passkeys" is used by default when importing passkeys.

I cannot understand why the difference in storage. github is stored diretly in the "Imported Passkeys" folder, while gitlab is stored in "KeePassXC-Browser-Passwords" subfolder of "Imported Passkeys"

[varjolintu]

I cannot understand why the difference in storage. github is stored diretly in the "Imported Passkeys" folder, while gitlab is stored in "KeePassXC-Browser-Passwords" subfolder of "Imported Passkeys"

Is it possible that you've accidentally arranged the groups? You can always move the credentials around.

[debmint]

On Thu, 2024-08-15 at 20:36 -0700, Sami Vänttinen wrote: > Now it seems that If I try to log in to GitLAB, it pauses on prompt > to touch device. If I cancel and retry, it works. I saw on > discussion in maybe keepassxc-browser repo a few months ago that > gitlab was not yet functional. One odd thing, GitLab passkeys are > stored under "KeePassXC-Browser-Passwords", and GitHub passkeys are > stored under "Imported Passkeys". I wonder what is the difference? "Imported Passkeys" is used by default when importing passkeys.

I wonder if the fact that GitLab's passkey is stored differently is due to the fact that they possibly use some different protocol or something?

[varjolintu]

GitLab has some problems during the passkeys development. I need to recheck to current situation.

[debmint]

On Fri, 2024-08-16 at 22:34 -0700, Sami Vänttinen wrote: GitLab has some problems during the passkeys development. I need to recheck to current situation.

As I mentioned in a previous post, it hangs, so to speak, on first challenge, but it appears that if you retry, it succeeds.

[varjolintu]

It seems that there might be a script at the page that tries to authenticate with a passkey immediately before the page content (or content script) is loaded, causing the extension not to detect the API call.

[debmint]

On Mon, 2024-08-19 at 20:38 -0700, Sami Vänttinen wrote: It seems that there might be a script at the page that tries to authenticate with a passkey immediately before the page content (or content script) is loaded, causing the extension not to detect the API call

Thank you for the reply.  Your answer agrees with the suspicion I had come up with.

[debmint]

On Tue, 2024-09-03 at 21:10 -0700, Sami Vänttinen wrote: > I cannot understand why the difference in storage. github is stored > diretly in the "Imported Passkeys" folder, while gitlab is stored > in "KeePassXC-Browser-Passwords" subfolder of "Imported Passkeys" Is it possible that you've accidentally arranged the groups? You can always move the credentials around.

No, I don't think so.  Github went directly into "Imported Passkeys", and, as a matter of fact, I deleted my gitlab passkey and created a new one, and, just like before, it went into the "KeePassXC-Browser Passwords" subgroup of "imported...".   I have another account which went in with gitlab, also.  Oh, well, just as long as they work ...