Bug 30066 - pam's (common-auth) univention-ucc-update-nss does not work for ssh sessions (UCC-remote)
pam's (common-auth) univention-ucc-update-nss does not work for ssh sessions ...
Status: CLOSED WONTFIX
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Documentation
unspecified
Other Linux
: P5 normal
: ---
Assigned To: Docu maintainers
: interim-4
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-18 12:12 CET by Moritz Muehlenhoff
Modified: 2023-06-28 10:32 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2013-01-18 12:12:03 CET
This should be documented

+++ This bug was initially created as a clone of Bug #30049 +++

If a user is created, he is not known in nss on ucc thin clients, but a "local"
login with that user is possible (kerberos authentication). Then common-auth
executes univention-ucc-update-nss and updates the passwd. 

But ssh does not allow logins with unknown usernames. For a remote session, the
"unknown" user logs on to the thin client (local login -> common-auth ->
univention-ucc-update-nss -> user is known on the thin client). Then the
sessions script for the remote session tries to establish a ssh connection to
the desktop server. But this ssh connection is not possible, as long as the
user is unknown on the desktop server. 

On ucc desktop servers the nss information will be updated every five minutes. 
So you have to wait 5 minutes before you can log on with a new user to a UCC
remote session.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-01-28 09:03:45 CET
This has been fixed code-wise in UCC, so the workaround no longer needs to be documented.