Bug 54924 – Wrong SSL certificate expiry warning, when using Let's encrypt

Bug 54924 - Wrong SSL certificate expiry warning, when using Let's encrypt


Summary:	Wrong SSL certificate expiry warning, when using Let's encrypt

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	SSL
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-07-04 07:31 CEST by Daniel Tröder
Modified:	2022-07-04 10:27 CEST (History)
CC List:	1 user (show)

See Also:	53909 51787
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?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034
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:

Attachments
Screenshot showing Chrome SSL certificate info and UMC warning (58.69 KB, image/png) 2022-07-04 07:31 CEST, Daniel Tröder	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Tröder

2022-07-04 07:31:49 CEST

Created attachment 10961 [details]
Screenshot showing Chrome SSL certificate info and UMC warning

# univention-app info
UCS: 4.4-9 errata1262
Installed: letsencrypt=1.2.2-20 nagios=4.3 samba4=4.10 self-service=4.0 self-service-backend=4.0 ucsschool=4.4 v9

A customer uses the Let's encrypt app to automatically update it's public SSL certificates. Yesterday an update from 4.4-4 to 4.4-9 errata1262 was installed. Since then the logged in administrator is shown a warning that the SSL certificate will expire soon - which is wrong. See attached screenshot.

Comment 1 Daniel Tröder

2022-07-04 08:24:14 CEST

Just got word, that the warning was there before the update, so at least since 4.4-4.

Comment 2 Florian Best

2022-07-04 10:27:32 CEST

See also Bug #53909, Bug #51787.