Bug 56625 - Deleting the defaultADconnection the wizard does not find a connection when restarting and does not create a new default connection on its own.
Deleting the defaultADconnection the wizard does not find a connection when r...
Status: NEW
Product: UCS
Classification: Unclassified
Component: Office 365
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-09-19 09:17 CEST by Christina Scheinig
Modified: 2023-09-19 10:40 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.017
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023081721000327
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 Christina Scheinig univentionstaff 2023-09-19 09:17:37 CEST
During troubleshooting a customer deleted the defaultADconnection. The wizard does not find a connection when restarting and does not create a new default connection on its own. 
Instead the error message "Internal server error" appears. After setting the default AD connection it works again.

From a purely logical point of view, I think the wizard should automatically check whether the "default value" is already set and then create a new one in case of doubt. The error message "Internal server error" is not very descriptive. Actually it should say that no M365 connection is available in "uninitialized" status and a new one has to be created.

5.0-4 errata783
Comment 1 Nico Gulden univentionstaff 2023-09-19 10:40:36 CEST
Related request for improving the documentation about the Microsoft 365 Connector at bug #56626.