Bug 13541 - UMC AD Connector: Resync after configuration changes
UMC AD Connector: Resync after configuration changes
Status: NEW
Product: UCS
Classification: Unclassified
Component: UMC - AD Connector
UCS 4.2
All All
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-02-25 10:25 CET by Ingo Steuwer
Modified: 2018-04-14 14:15 CEST (History)
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 after Product Owner Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Steuwer univentionstaff 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 univentionstaff 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 univentionstaff 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.