Bug 54877 – Same name of ipmanagedclients in different ous

Bug 54877 - Same name of ipmanagedclients in different ous


Summary:	Same name of ipmanagedclients in different ous

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-06-17 11:44 CEST by Christina Scheinig
Modified:	2022-06-17 11:45 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.034
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2022061621000209
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christina Scheinig

2022-06-17 11:44:21 CEST

In different ous it is possible to create ipmanagedClients with the same name.
However, there is then only one host entry with two IP addresses in the DNS.
If you also use certificates for the Hosts, then only one certificate is created.

udm dns/host_record list --filter relativeDomainName=fooBar
relativeDomainName=fooBar
DN: relativeDomainName=fooBar,zoneName=schein.qa,cn=dns,dc=schein,dc=qa
  a: 10.200.43.2
  a: 10.200.43.4
  name: fooBar
  zonettl: None
--------------
univention-s4search --cross-ncs --show-binary dc=fooBar

# record 1
dn: DC=fooBar,DC=schein.qa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=schein,DC=qa
objectClass: top
objectClass: dnsNode
instanceType: 4
whenCreated: 20220617074348.0Z
uSNCreated: 5611
showInAdvancedViewOnly: TRUE
name: fooBar
objectGUID: 89fbd3ff-cff2-48a7-b25e-87582fb9b0c5
objectCategory: CN=Dns-Node,CN=Schema,CN=Configuration,DC=schein,DC=qa
dc: fooBar
dnsRecord:     NDR: struct dnsp_DnssrvRpcRecord
        wDataLength              : 0x0004 (4)
        wType                    : DNS_TYPE_A (1)
        version                  : 0x05 (5)
        rank                     : DNS_RANK_ZONE (240)
        flags                    : 0x0000 (0)
        dwSerial                 : 0x00000001 (1)
        dwTtlSeconds             : 0x00000384 (900)
        dwReserved               : 0x00000000 (0)
        dwTimeStamp              : 0x00000000 (0)
        data                     : union dnsRecordData(case 1)
        ipv4                     : 10.200.43.2

dnsRecord:     NDR: struct dnsp_DnssrvRpcRecord
        wDataLength              : 0x0004 (4)
        wType                    : DNS_TYPE_A (1)
        version                  : 0x05 (5)
        rank                     : DNS_RANK_ZONE (240)
        flags                    : 0x0000 (0)
        dwSerial                 : 0x00000001 (1)
        dwTtlSeconds             : 0x00000384 (900)
        dwReserved               : 0x00000000 (0)
        dwTimeStamp              : 0x00000000 (0)
        data                     : union dnsRecordData(case 1)
        ipv4                     : 10.200.43.4

whenChanged: 20220617082206.0Z
uSNChanged: 5613
distinguishedName: DC=fooBar,DC=schein.qa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=schein,DC=qa


In contrast to this the windowscomputer creation is checked via username which not exist at the ipmanagedClient attribute.

Notification
The LDAP object could not be saved: The username is already in use as username or as groupname : winni$