829a096ba1
When verification failed using a specific authentication service we're currently restarting the whole user authentication system, which leads to lots of unneeded operations (reinitializing a new user verifier proxy, restarting all the gdm workers with the relative PAM modules and so on). And this makes also debugging of login problems more complicated, given we're cluttering the journal with repeated data. However, at reauthentication failure GDM has already set up for us an user verifier that we can use reuse to start only the service that had a failure. So when possible, just start a new service instead of rebooting the whole authorization process. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1622> |
||
---|---|---|
.. | ||
authPrompt.js | ||
batch.js | ||
credentialManager.js | ||
loginDialog.js | ||
oVirt.js | ||
realmd.js | ||
util.js | ||
vmware.js |