Bug 45702

Summary: diagnostic test for SSL certificates fails with Lets Encrypt certs
Product: UCS Reporter: Dirk Ahrnke <da>
Component: UMC - System diagnosticAssignee: UMC maintainers <umc-maintainers>
Status: CLOSED MOVED QA Contact: UMC maintainers <umc-maintainers>
Severity: normal    
Priority: P5 CC: best, heidelberger
Version: UCS 4.2   
Target Milestone: ---   
Hardware: Other   
OS: All   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=40228
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?: 3: Will affect average number of installed domains How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.103 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:

Description Dirk Ahrnke 2017-11-10 17:06:09 CET
Reported in https://help.univention.com/t/problems-in-systemdiagnose/7106

It appears that the fix for #40228 fails for certificates issued by Lets Encrypt.
Comment 1 Florian Best univentionstaff 2017-11-28 14:11:16 CET
It might be fixed with the latest App upgrade of letsencrypt?

Let's encrypt 1.0.4-6 (UCS 4.1)
Let's encrypt 1.1.1-2 (UCS 4.2)
Comment 2 Dirk Ahrnke 2017-11-28 15:13:53 CET
After upgrading to version 1.1.1-2 the diagnotics did not show the error anymore.
Sidenote: The update did not retain the configuration. All SSL/TLS services used the default UCS-certs afterwards so I had to run setup-letsencrypt again. I dont know if this is the desired behaviour but it works for me.
Comment 3 Florian Best univentionstaff 2017-11-28 15:26:31 CET
(In reply to Dirk Ahrnke from comment #2)
> After upgrading to version 1.1.1-2 the diagnotics did not show the error
> anymore.
> Sidenote: The update did not retain the configuration. All SSL/TLS services
> used the default UCS-certs afterwards so I had to run setup-letsencrypt
> again. I dont know if this is the desired behaviour but it works for me.

Thank you for your sidenote. I send an internal feedback.