Bug 40414 – S4-Connector should store only non-rejected DNs as premapped

Bug 40414 - S4-Connector should store only non-rejected DNs as premapped


Summary:	S4-Connector should store only non-rejected DNs as premapped

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-11 18:04 CET by Arvid Requate
Modified:	2019-01-03 07:18 CET (History)
CC List:	1 user (show)

See Also:	40380
What kind of report is it?:	Development Internal
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):	Error handling
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 Arvid Requate

2016-01-11 18:04:38 CET

The S4-Connector should only store valid DN-relations to 'DN Mapping CON' and 'DN Mapping UCS'. In the case of Bug 40380 Comment 5 an invalid DN relation was stored and then the S4-Connector insists to use that instead of searching again. The S4-Connector should store these DN-relations only for successful synchronizations.

At least two functions rely on these DN-relation tables:

* samaccountname_dn_mapping
* dns_dn_mapping

They attempt to determine the target DN from the tables and if something is stored then it is taken as "premapped".


In addition to this approach of avoiding invalid entries it might be necessary to make the S4-Connector "forget" a premapping if a reject is encountered at some point.

Comment 1 Stefan Gohmann

2019-01-03 07:18:27 CET

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.