Univention Bugzilla – Bug 33861
move passwd listener (ucc-nss-passwd.py) to UCS?
Last modified: 2019-01-03 07:18:16 CET
UCC uses a local passwd (and group) file instead of libnss-ldap. This file is copied from the ldap/server/name UCS server with univention-ucc-update-nss. For this to work the ucc integration packages must be installed on the UCS server, because ucc-management-integration contains the listener module that creates the passwd file. This can be a pain in an ucs@school environment with lots of school dc's and ucc clients. If univention-ucc-ucsschool-integration is installed on the UCC clients, ldap/server/name is set to the school dc and univention-ucc-update-nss on the client fails until the ucc-management-integration is installed on (all) school dc's (so that they can provide the passwd file, created by the listener module). Maybe better to move the listener ucc-nss-passwd.py from UCC to UCS (all dc's). Then (a) univention-ucc-update-nss would always work regardless to which UCS dc ldap/server/name is set and if ucc is installed on that server (b) selective replication would work for ucc clients (as the passwd is than created and copied from the school dc)
Moving to product UCS
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.