PhilippC / PhilippC/keepass2android

[BUG] Login on Firefox never works the first time

Open
#2,682 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.2k
Forks
478
Avg merge
1h 4m
Merged PRs (30d)
2

Description

Checks
  • I have read the FAQ section, searched the open issues, and still think this is a new bug.
Describe the bug you encountered:

Possibly related to #2422

I recently switched to Keepass2Android but autologin doesn't works reliably. I consistently experience the following:

  1. Open a page in Firefox Mobile that requires HTTP BASIC Auth (over https)

  2. Login form appears and I can choose to fill the form using Keepass2Android:

image
  1. I unlock Keepass2Android and choose the correct entry

  2. back to firefox it looks like Firefox being busy with the second server request but no request is sent the server at all. I can say that because I run the server myself and observed all traffic to it. Normally the authenticated request should be sent to the server at this point

image
  1. About 30 seconds later the server message appears that the client did not authenticate successfully. I'm pretty sure that's the HTTP response for the first (any only) request (where Firefox learned that a password is required).
image
  1. I tap on reload in Firefox and the login form appears again but this time the keyboard offers to fill in specific login credentials (along with the generic "fill with Keepass2Android"):
image
  1. Tapping on these credentials fills the form and submits it, then the page is correctly authenticated

Additional info:

  • The login procedure works flawlessly when I'm not using Keepass2Android.
  • It is not related to this website. This happens on all sites when using Keepass2Android.
  • The Keepass database originally had been initialized by importing credentials from Firefox (using KeePassXC), if that matters.

Versions:

  • Firefox 131.0 (Build #2016046167)
  • Keepass2Android 1.10-pre with Quickunlock enabled (fingerpring) and a beer sent
  • Samsung Galaxy S24+
Describe what you expected to happen:

I expect the page to be authenticated at the first try

What version of Keepass2Android are you using?

1.10-pre

Which version of Android are you on?

14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the reported flow in Firefox Mobile with Keepass2Android 1.10-pre on Android 14: open an HTTPS HTTP Basic Auth page, fill credentials through Keepass2Android, and observe the missing authenticated request. Compare the first attempt with the successful reload flow; done means authentication succeeds on the first try.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
authentication, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.