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

Auto-fill of TOTP with KeePassXC inserts username #22967

Open
4 tasks done
janbaum opened this issue Nov 23, 2024 · 0 comments
Open
4 tasks done

Auto-fill of TOTP with KeePassXC inserts username #22967

janbaum opened this issue Nov 23, 2024 · 0 comments

Comments

@janbaum
Copy link

janbaum commented Nov 23, 2024

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

When using auto-fill function of KeePassXC Browser integration, username and password inserts as expected.
Afterwards TOTP field appears.

Here the auto fill function (the keepass logo next to the input fields) inserts the username instead of the curretn TOTP token.

Describe the behavior you expected

Auto fill function on TOTP field should fill in the current TOTP token.

This works just fine with other services, for example Nextcloud.

Steps to reproduce the issue

  1. Install KeePassXC extension in Browser (Firefox, Chromium, etc)
  2. Enable 2FA with KeePassXC as Authenticator App.
  3. Try to Login in with auto fill feature of KeePassXC extension.

What version of Home Assistant Core has the issue?

2024.11.3

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 132.0, Version 131.0.6778.69 (Official Build) Arch Linux (64-bit)

Which operating system are you using to run this browser?

Manjaro

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

image

I am not a developer, so I am still unsure whether this Issue belongs here. I still opened it issue here, because this feature works with all other services I use this with (for example Nextcloud, GitHub, aso...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant