Description Christina Scheinig 2019-10-01 11:36:33 CEST

A computeraccount is not shown in the UMC computers module but in the ldap-directory module.

The computeraccount lacks the Kerberos attributes, the corresponding objectClass and univentionServerRole: windows_client

The computeraccount looks like this:

# test, computers, schein.ig
dn: cn=test,cn=computers,dc=schein,dc=ig
macAddress: 00:19:99:6f:11:e6
cn: test
objectClass: top
objectClass: univentionHost
objectClass: univentionObject
objectClass: sambaSamAccount
objectClass: person
objectClass: shadowAccount
objectClass: univentionWindows
objectClass: posixAccount
uidNumber: 2018
sambaAcctFlags: [W          ]
uid: test$
aRecord: 10.200.43.22
loginShell: /bin/false
univentionObjectType: computers/windows
displayName: test
associatedDomain: schein.ig
sn: test
univentionNetworkLink: cn=default,cn=networks,dc=schein,dc=ig
homeDirectory: /dev/null
gidNumber: 1005
sambaPrimaryGroupSID: S-1-5-21-2438365080-1175145288-4246282840-11011
sambaSID: S-1-5-21-2438365080-1175145288-4246282840-1122
description: aaa
----------

The identity filter in  
/usr/share/pyshared/univention/admin/handlers/computers/windows.py
---
def identify(dn, attr, canonical=0):
        return 'univentionHost' in attr.get('objectClass', []) and 'univentionWindows' in attr.get('objectClass', []) and 'windows_domaincontroller' not in attr.get('univentionServerRole', [])
---
should find the computer, but the computer is not shown in the UMC.

Searching via univention-ldapsearch '(&(&(objectClass=univentionHost)(objectClass=univentionWindows))(!(univentionServerRole=windows_domaincontroller)))' this filter finds the computeraccount.