Hello, While the 2-Factor validation feature brought by pam_google_authenticator.so could successfullly login through the GDM or LightDM, the KDE's own screen-greeter seems to have no support on 2FA. I assume the configure file is /etc/pam.d/kde, but after alteration there is no way to login into the system by greeter itself. I've found there are also some enquiries to this issue before: https://www.spinics.net/lists/kde/msg21998.html https://askubuntu.com/questions/972710/two-factor-authentication-with-kubuntu-screensaver Hopes there could be possible solutions adhere or in the later KDE versions. Thanks
You're mixing up terms. kscreenlocker is not a login interface equivalent to GDM or lightDM
(In reply to David Edmundson from comment #1) > You're mixing up terms. > > kscreenlocker is not a login interface equivalent to GDM or lightDM I understand that kscreenlocker is just a lock-up tool like xscrrensaver, etc. DM is another tool which 'introduce' the KDE or other DE. Under the normal KDE experience, a user may use the kscreenlocker to lock up their desktop session, instead of log out to use DM-related login interface. Upon the issue, when I change the auth line about 2FA tools in 'required' mode in /etc/pam.d/system-login, the lightDM works perfectly, but when you enter the KDE, using kscreenlocker to lock your session, their is the problem. When I change the line into 'sufficient' mode, the kscreenlocker works! It seems that there should be the implementation to help entering the verification code I have tried GDM, there is no such a issue in the previous login or later lock screen. Thanks.
Thank you for reporting this feature request in KDE software. As it has been a while since it was reported, can we please ask you to see if it's still relevant with a recent software version? Like Plasma 5.25, or ideally 5.26? If so, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!