Public bug reported:
[ Impact ]
On Ubuntu 26.04 (resolute) with authd 0.6.1ubuntu0.1 and the authd-msentraid
broker, the GNOME "login" keyring is never unlocked automatically at login,
even when the keyring password is identical to the user's local password.
Every session starts with a "Unlock Login Keyring" prompt.
This was reported upstream as canonical/authd#944 and fixed by
canonical/authd#1190 ("pam: Set PAM_AUTHTOK on successful authentication"),
which shipped in authd 0.7.0 (26.10). resolute still has 0.6.1ubuntu0.1 and
there is no SRU in progress.
On managed fleets this is not only a UX issue. The Microsoft Intune agent
for Linux (intune-portal) stores its session in the keyring. While the
keyring is locked, every check-in fails:
Failed to checkin with Intune: Authentication failed: User interaction is
required (OneAuth error 2)
and the device stops reporting compliance until the user unlocks the
keyring. Users who dismiss the prompt silently fall out of management. We
see this on a fleet of 26.04 LTS laptops enrolled in Intune with authd as
the login method.
Verified on 26.04 with authd 0.6.1ubuntu0.1:
- Login with local password -> keyring prompt shown, keyring locked
(org.freedesktop.Secret.Collection Locked = true) until unlocked manually.
- With the keyring locked, intune-agent check-in fails with the error above.
- After unlocking the keyring, the same check-in succeeds immediately.
[ Test Plan ]
1. On 26.04 with authd and authd-msentraid, log in once as an Entra user and
create a "login" keyring with the same password as the local password;
set it as default.
2. Log out and log in again with the local password.
3. Check the keyring state:
busctl --user get-property org.freedesktop.secrets \
/org/freedesktop/secrets/collection/login \
org.freedesktop.Secret.Collection Locked
Current package: "b true" and an unlock prompt is shown.
Fixed package: "b false" and no prompt.
4. Regression checks: login and screen unlock still work for authd users
and for local (pam_unix) users; sudo still works for both; login with a
new local password set via device authentication still works.
[ Where problems could occur ]
The change makes the authd PAM module set PAM_AUTHTOK after a successful
authentication. Other modules later in the PAM stack can now see the
token, so a misbehaving stack could lead to unexpected authentication
behaviour or, in the worst case, failed logins. The scope is limited to
authentications handled by authd; local users authenticated by pam_unix
are not affected.
[ Other Info ]
Upstream issue: https://github.com/canonical/authd/issues/944
Upstream fix: https://github.com/canonical/authd/pull/1190
Released in: authd 0.7.0 (stonking)
Environment:
Ubuntu 26.04.1 LTS (resolute)
authd 0.6.1ubuntu0.1 (installed and candidate; resolute-updates/-security)
authd-msentraid snap 0.5.0 (rev 474, 0.x/stable)
gnome-keyring 50.0-1
intune-portal 1.2607.4-resolute
** Affects: authd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2173924
Title:
SRU] Login keyring is not unlocked at login with authd on 26.04 (fixed
upstream in 0.7.0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2173924/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs