Univention Bugzilla – Bug 33674
UMC-Module for AD Connector administration
Last modified: 2021-10-12 13:23:32 CEST
A UMC module would be helpful which shows the rejected objects and why these objects have been rejected. One should be able to resync or ignore the rejects. The log file should also be shown.
*** Bug 13501 has been marked as a duplicate of this bug. ***
*** Bug 13499 has been marked as a duplicate of this bug. ***
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.
This issue has been filed against UCS 3.2. UCS 3.2 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.
Simply adding a "ignore" button is dangerous IMHO. A reject shows that some change needed to be synchronized and if you drop it, that object might be out of sync. If we add a button, users click it. So if we want that feature, we should immediately trigger a resync for that object, so the Connector get's another chance. Regarding the other point of the feature request "why these objects have been rejected": Felix proposed adjusting the Connector to store the reason for a reject into a database (probably the existing sqlite db). I guess it would not be too difficult to store traceback.format_exc() in case of exceptions.
For the second part of Comment 5 I've now created a Bug 46355, first for the S4-Connector, which may then be ported to the AD-Connector if successful. As discussed, I would suggest interpreting the "ignore" feature requested by Stefan literally as "ignore rejects" and not as "delete rejects". So, in my imagination, the administrator could click on "ignore this reject" and the module would mark it with an "ignore" flag in the sqlite database. The AD-Connector would need to be adjusted to consider the new "ignore" flag. This would help the user to stop the AD-Connector logging the repeating same traceback. And it would avoid situations where a user drops arbitrary rejects (which may occur temporarily even under normal conditions). Resulting situations would be hard to debug in a support case in case a user complains about issues with non-synchronized changes.
This issue has been filled against UCS 3.2. The maintenance with bug and security fixes for UCS 3.2 has ended on 30st of November 2016. Customers still on UCS 3.2 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.