Fails to detect proper fields in Fortuneo bank (detailed report)

Kee browser extension
1

Setup

Vivaldi : 4.0.2312.27 based on chromium 91.0.4472.102
Keepass : 2.48.1
KeePassRPC : 1.14
Kee Browser extension : 3.9.5

Problem

On the bank login page (Identification - Votre Accès Client Fortuneo, pour gérer en ligne l'ensemble de vos comptes : banque, assurance-vie, Bourse, livret...), Kee detects the password field as the id field, no matter the settings and fails to detect the id field.

Id field
image

password field
image

Keepass Settings
image
image

KPRPC JSON

{
	"version": 1,
	"formFieldList": [
		{
			"name": "PASSWD",
			"displayName": "KeePass password",
			"value": "{PASSWORD}",
			"type": "FFTpassword",
			"id": "",
			"page": 1,
			"placeholderHandling": "Default"
		},
		{
			"name": "LOGIN",
			"displayName": "KeePass username",
			"value": "{USERNAME}",
			"type": "FFTusername",
			"id": "",
			"page": 1,
			"placeholderHandling": "Default"
		}
	],
	"alwaysAutoFill": false,
	"neverAutoFill": true,
	"alwaysAutoSubmit": false,
	"neverAutoSubmit": true,
	"priority": 0,
	"hide": false,
	"blockHostnameOnlyMatch": false,
	"blockDomainOnlyMatch": true
}

I tried to play with several extension white list settings for the page https://mabanque.fortuneo.fr/fr/identification.jsp
image

Any idea ?

2

It looks like they have designed the page to prevent assistive technology like Kee from working correctly. Specifically, they rely on Javascript for form submission and have split each form field into entirely separate forms.

The latter reason is why you see only one field detected - Kee will actually find both but has to decide which form is the actual sign-in form and pick just one to fill your data into (and that’s the one where it will position the Kee icons into each field in the form).

By adjusting the form field configuration in the entry and probably also the whitelist, you should be able to get Kee to pick the form containing the ID field instead but I don’t think that will be all that helpful since the password field will then no longer work.

Are you sure that Kee fills the ID into the password field? I would expect that this part would work correctly, although only until the page’s own Javascript might try to break things.

If you’re not in an environment where you’re comfortable having the webpage remember your user ID, I’d suggest copy/pasting that into the correct field first and then if you ask Kee to fill the password field, it should work. Although again, their Javascript may mean that you will have to disable the auto-submit feature and click the button yourself.

By the way, for any future problematic sites enabling debug logging will give you more clues about what is going on with a particular page and might save some time spent through trial and error.

3

Are you sure that Kee fills the ID into the password field? I would expect that this part would work correctly, although only until the page’s own Javascript might try to break things.

I suspect it because when I fill the ID and use Kee to fill the password, the log in fails. And when click on the kee icon on the field, it shows me the ID in the list but I’m not sure it is relevant.
image

Here is the web console output. I don’t the browser console equivalent for chromium browsers.

It returns No password field found in this form and either there are no other fields or no whitelisted text field or form element although my rule.

image
image

I use keepass autofill as a workaround for this site.