Bug 47091 - Give the user more information how to handle "Could not connect to AD Server" messages
Give the user more information how to handle "Could not connect to AD Server"...
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.3
Other Linux
: P5 normal (vote)
: UCS 4.3-0-errata
Assigned To: Arvid Requate
Felix Botner
Depends on: 44478
  Show dependency treegraph
Reported: 2018-05-28 12:06 CEST by Arvid Requate
Modified: 2018-06-06 16:16 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 3: Will affect average number of installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.309
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number: 2018041621001051
Bug group (optional): External feedback
Max CVSS v3 score:
requate: Patch_Available+

output_exception_for_feedback.patch (4.26 KB, patch)
2018-05-28 12:06 CEST, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2018-05-28 12:06:32 CEST
Created attachment 9541 [details]

We should further improve the feedback message for connectionFailed and failedADConnect exceptions because we still get feedback of this kind:

Configuring Active Directory connection: Could not connect to AD Server <FQDN REDACTED>. Please verify that username and password are correct.

Role: domaincontroller_master

+++ This bug was initially created as a clone of Bug #44478 +++
Comment 1 Arvid Requate univentionstaff 2018-05-28 12:22:42 CEST
c7a7936f04 | Improve error feedback
14bd47183b | Advisory
1779a36f84 | Fix typo
a3b1f1632c | Advisory
Comment 2 Felix Botner univentionstaff 2018-05-30 12:57:55 CEST
OK - univention-ad-connector
OK - yaml
Comment 3 Erik Damrose univentionstaff 2018-06-06 16:16:43 CEST