PhilippC / PhilippC/keepass2android
[BUG] Strange behavior with AutoOpen/Child Database
Nobody has claimed this yet.
- 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:
On Desktop im using a lot the AutoOpen Feature or better Child Databases. I enter the webdav url without credentials in the url field and set username an password in the fields IocUsername and IocPassword. I can also use this entry successfully with KP2A.
However, when i change something in such a entry within KP2A and save it again, the username and password becomes part of the URL. It keeps the custom fields IocUsername and IocPassword and additionally has the credentials part of the URL like https://username:password@domain.com/path/to/database.kdbx. This is also the case, when i change only a custom field like Enable:true/false.
Can you please keep the original URL until i change it really?
Describe what you expected to happen:
If i change something in this entry within KP2A, the url field should only change, if i change the url field directly.
What version of Keepass2Android are you using?
1.14 r-1
Which version of Android are you on?
15
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the AutoOpen/Child Database behavior in Keepass2Android 1.14 r-1 using a WebDAV URL, IocUsername, and IocPassword, then edit a non-URL field. Trace the save path for these entries and verify that the original URL remains unchanged unless the URL itself is edited, without embedding credentials in it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100