[Hardening] F-06: 2FA Field Set as Password Causes Password Manager Issues.

### The required feature described as a wish

**Description:** The 2FA input is defined as type="password". Password managers treat it like a regular password field, so they may save or autofill the 2FA code. This can overwrite the stored password and lock the user out of their account. The field was likely set this way to hide the Static PIN from bystanders or during screen sharing.

**Affected Components:** Management UI

**Impact:** Password managers may replace saved passwords with 2FA codes. This can lock users out and lead them to choose weaker passwords or store them insecurely.

**Steps to Reproduce:**
- Log in to the CloudStack Management UI with a user that has 2FA enabled.
- Enter valid credentials and continue to the 2FA screen.
- Inspect the 2FA input field in the browser’s developer tools.
- Confirm it is set to type="password".

**Recommended Remediation:** Change the 2FA input field to type="number" and add autocomplete="one-time-code". This informs password managers of the field's actual meaning.

Also, consider combining the password and 2FA into a single form. This way, attackers can’t tell which part failed, making password attacks harder.

從 issue #13337 中描述的 CloudStack Management UI 2FA 登入表單開始，並檢視已合併的 pull request #13723，以了解已完成的工作。當密碼管理器將 2FA 欄位識別為一次性代碼而不是一般密碼時，即表示完成；而個別的表單組合建議仍屬於更廣泛的考量事項。

由索引模型根據 Issue 內容生成。