Bug 56693 – AD-Connector resync

Bug 56693 - AD-Connector resync


Summary:	AD-Connector resync

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-10-02 15:25 CEST by Mirac Erdemiroglu
Modified:	2023-10-04 10:38 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a 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.046
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023092921000204, 2023092821000181
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 Mirac Erdemiroglu

2023-10-02 15:25:55 CEST

After the connector tries to resync 10 times by default, it stops and the respective rejects simply remain unprocessed.


Here is the UCRV that determines the number of resyncs

connector/ad/max_retry_rejected

 The number of attempts to resync rejected changes from AD to UCS. You can resync these changes manually using the /usr/share/univention-ad-connector/resync_object_from_ad.py script.

 Categories: service-adcon

 Default: 10


I find this a bit inconvenient, because it would also be very helpful for the customer, if the ad-connector itself tries to resync everything 24 hours. 


This would save the customer the effort of changing the UCRV and restarting the connector.