Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keepassxc browser passkey doesn't work with one of the containers #2636

Closed
2 tasks done
Ajnasz opened this issue May 7, 2024 · 1 comment
Closed
2 tasks done

Keepassxc browser passkey doesn't work with one of the containers #2636

Ajnasz opened this issue May 7, 2024 · 1 comment
Labels
bug Something is broken!

Comments

@Ajnasz
Copy link

Ajnasz commented May 7, 2024

Before submitting a bug report

  • I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
  • I searched for existing reports to see if it hasn't already been reported

Step to reproduce

  1. I opened github within my Work container
    1. I try to log in with a passkey
    2. I get an Authentication failed error message
    3. In the console I can see Permission denied to access property "then" error message
  2. I open github within another conainer
    1. I try to log in with a passkey
    2. I log in successfully

Actual behavior

I can't log in with passkey in the Work container

Expected behavior

I can log in with any container

Additional informations

I reported the issue to the keepassxc-browser extension, before I tried to log in with another container: keepassxreboot/keepassxc-browser#2193
What is written there, that the data which would be used by the keepassxc extension is some kind of Restricted object, which can't be accessed.

I would be happy to debug this issue, because most probably it's a misconfiguration only on my side. If you can help me how can I dump the configurations of the containers I can compare them to see what could be wrong.

Please also share if you know a way how I can copy the sites from the affected container to a new one, so I wouldn't need to setup everything if I can't solve the issue.

Provide a copy of Troubleshooting Information page (optional)

No response

@Ajnasz Ajnasz added the bug Something is broken! label May 7, 2024
@Ajnasz
Copy link
Author

Ajnasz commented May 7, 2024

I figured out the issue and it turned out that the issue was that my user agent was changed to chrome in the container, so the isFirefox() function returned false, so the firefox specific code was never called.

@Ajnasz Ajnasz closed this as completed May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken!
Projects
None yet
Development

No branches or pull requests

1 participant