Username is put in wrong input field in Adminer

[zdenak11]

Username is put in wrong input field in Adminer

• Passbolt Version: 3.3.1
• Platform and Target: -- Browser: Chrome -- Server: All servers based on https://www.adminer.org/en/

What you did

Click to insert credentials in passbolt browser extension

What happened

Username was inserted into field for hostname instead of username. Password was inserted correctly.

HTML of login form

<form action="" method="post">
<div></div>
<table cellspacing="0" class="layout">
<tbody><tr><th>System</th><td><select name="auth[driver]"><option value="server" selected="">MySQL</option><option value="sqlite">SQLite 3</option><option value="sqlite2">SQLite 2</option><option value="pgsql">PostgreSQL</option><option value="oracle">Oracle (beta)</option><option value="mssql">MS SQL (beta)</option><option value="mongo">MongoDB (alpha)</option><option value="elastic">Elasticsearch (beta)</option></select><script nonce="">qsl('select').onchange = function () { loginDriver(this); };</script>
</td></tr><tr class=""><th>Server</th><td><input name="auth[server]" value="" title="hostname[:port]" placeholder="localhost" autocapitalize="off">
</td></tr><tr><th>Username</th><td><input name="auth[username]" id="username" value="" autocomplete="username" autocapitalize="off"><script nonce="">focus(qs('#username')); qs('#username').form['auth[driver]'].onchange();</script>
</td></tr><tr><th>Password</th><td><input type="password" name="auth[password]" autocomplete="current-password">
</td></tr><tr><th>Database</th><td><input name="auth[db]" value="" autocapitalize="off">
</td></tr></tbody></table>
<p><input type="submit" value="Login" class="">
<label><input type="checkbox" name="auth[permanent]" value="1">Permanent login</label>
</p></form>

[Benj1er]

Hello @zdenak11,

Sorry for the delay and thanks for your report. This issue only occurs on the quickaccess autofill. An internal ticket (ref: PB-18374) has been created to fix this issue.

Best regards

[Benj1er]

Hello @zdenak11,

The issue has been fixed in v4.9.0. v4.9.0 is already available on chrome and will be available on firefox and edge in a few days. Please feel free to reopen it if the issue persists.

Best regards