Univention Bugzilla – Bug 49643
sync_to_ucs: reject for DC=@ SOA record after AD-Takeover
Last modified: 2019-06-19 15:52:44 CEST
Created attachment 10061 [details] handle_uppercase_DC_attribute.patch During a support case we found rejects in sync_to_ucs for DC=@ SOA records after an AD-Takeover. Analysis showed that the objectClass=dnsNode records from AD had a mixed spelling of the 'DC' attribute. Some records had DC=@,DC=99.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=foo,dc=net DC=@ but the the S4-Connector expects lowercase 'dc' for the attribute itself. We already had the same thing for 'CN' vs 'cn'. The attached patch fixed the issue in the customer environement.
One liner looks nicer: dc = object['attributes'].get('dc', dc = object['attributes'].get('DC'))
dc = object['attributes'].get('dc', object['attributes'].get('DC'))
b1e5e280e4 | Avoid rejects when DNS records have an uppercase DC attribute 434a0e8251 | Advisory
d0e2da7540 | Improve coding style 941daa6051 | Advisory
OK: change looks good OK: sync 07.06.2019 14:37:07.077 LDAP (PROCESS): sync from ucs: [ dns] [ add] DC=@,DC=192.168.99.in-addr.arpa,CN=MicrosoftDNS,DC=DomainDnsZones,DC=school,DC=dev 07.06.2019 14:37:08.613 LDAP (PROCESS): sync to ucs: [ dns] [ modify] zoneName=192.168.99.in-addr.arpa,l=school,l=dev 07.06.2019 14:37:08.638 LDAP (PROCESS): sync to ucs: [ dns] [ modify] zonename=192.168.99.in-addr.arpa,l=school,l=dev 07.06.2019 14:37:15.167 LDAP (PROCESS): sync from ucs: [ dns] [ modify] dc=@,dc=192.168.99.in-addr.arpa,cn=microsoftdns,dc=domaindnszones,DC=school,DC=dev 07.06.2019 14:37:16.686 LDAP (PROCESS): sync to ucs: [ dns] [ modify] zonename=192.168.99.in-addr.arpa,l=school,l=dev OK: YAML
<http://errata.software-univention.de/ucs/4.4/155.html>