Bug 13541 – UMC AD Connector: Resync after configuration changes

Bug 13541 - UMC AD Connector: Resync after configuration changes


Summary:	UMC AD Connector: Resync after configuration changes

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - AD Connector
Version:	UCS 4.2
Hardware:	All All

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-02-25 10:25 CET by Ingo Steuwer
Modified:	2020-07-03 20:51 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Feature Request
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:

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 Ingo Steuwer

2009-02-25 10:25:28 CET

Nachdem ein laufender AD-Connector rekonfiguriert wurde kann man die Möglichkeit anbieten einen Resync durchzuführen -- muss aber entsprechend vor den Folgen warnen. Schritte:

- Beenden des Connectors
- Löschen der internal.cfg
- Resync auf das Listener-Modul
- Start des Connectors

Comment 1 Stefan Gohmann

2014-02-18 21:29:06 CET

This issue has been filed against the UCS version "unstable" which does not really exist. Please change the version value.

Comment 2 Stefan Gohmann

2017-06-16 20:35:48 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Ingo Steuwer

2020-07-03 20:51:12 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.