Univention Bugzilla – Full Text Bug Listing |
Summary: | cn=Subschema rejects | ||
---|---|---|---|
Product: | UCS | Reporter: | Janis Meybohm <meybohm> |
Component: | S4 Connector | Assignee: | Arvid Requate <requate> |
Status: | CLOSED FIXED | QA Contact: | Stefan Gohmann <gohmann> |
Severity: | normal | ||
Priority: | P5 | CC: | ebersbach, gohmann, jmm, markus.daehlmann |
Version: | UCS 3.2 | ||
Target Milestone: | UCS 3.2-4-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
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: | |||
Bug Depends on: | |||
Bug Blocks: | 36981 |
Description
Janis Meybohm
2014-09-22 10:40:49 CEST
Also reported from another customer. This looks very similar to Bug 35628 but still it must have a different cause. I adjusted two things in the connector: a) Don't attempt to sync cn=Subschema b) Log an error if EntryUUID is missing in a pickle file but continue Advisory: 2014-11-27-univention-s4-connector.yaml (In reply to Arvid Requate from comment #2) > I adjusted two things in the connector: > a) Don't attempt to sync cn=Subschema OK > b) Log an error if EntryUUID is missing in a pickle file but continue I'm unsure if it is the right way. I prefer not to continue, leave it as rejected and check the objects. Do we know which DNs / objects don't contain the UUID? Ok, objects without entryUUID will be treated as rejects. Package is rebuilt and advisory is updated. > Do we know which DNs / objects don't contain the UUID? "Servers SHALL generate and assign a new UUID to each entry upon its addition to the directory and provide that UUID as the value of the 'entryUUID' operational attribute." -- https://tools.ietf.org/html/rfc4530 So, elements that are not added to but instead generated by the LDAP server (like rootDSE and cn=Subschema) don't necessarily offer this attribute. The purpose of the attribute is to identify object wich may get (re)moved, so it makes sense that it's not assigned to rootDSE and cn=Subschema. YAML: OK Tests: OK Code review: OK |