Created attachment 88139 [details] Screenshot describes this issue. Issue reproduce steps ------------------------------- 1. Install and properly setup to use pam-google-authenticator package 2. Try to authenticate yourself using PolicyKit1-KDE Expected behavior ------------------------------- User successfully authenticated after input account password, then the TOTP generated by Google Authenticator Abnormal behavior -------------------------------- The "Verification code:" textbox appeared non-modifyable thus the authentication process can't complete.(as the attached screenshot shown) Reporter's environment -------------------------------- * Ubuntu 14.04LTS using kubuntu-ppa/backports PPA * polkit-kde-1 package version: 0.99.1-1
Downstream bug report: https://bugs.launchpad.net/ubuntu/+source/polkit-kde-1/+bug/1353704
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
I confirm this still happens, exactly as per original description
Created attachment 122823 [details] authentication required Screenshot: requesting root access to change printer settings, where the root user has google authenticator configured in PAM
Created attachment 122824 [details] Requesting verification code before password Verification code is being requested first, as when logging via terminal. Please remember the TOTP verification code can be made sufficient&optional via PAM. If that's the case, but the user wishes to login normally, the other authentication methods should follow. If the verification code is entered, it should let the user in. If the verification code is skipped or entered incorrectly, it should ask for a password, but as per screenshots, it's disabled, non editable.