Bug 45333 – Check if master and backup use correct SSL certificate

Bug 45333 - Check if master and backup use correct SSL certificate


Summary:	Check if master and backup use correct SSL certificate

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - System diagnostic
Version:	UCS 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-09-06 17:15 CEST by Sönke Schwardt-Krummrich
Modified:	2020-07-03 20:54 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
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
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 Sönke Schwardt-Krummrich

2017-09-06 17:15:58 CEST

Most UMC modules that contact the UCS master via UMCP rely on the fact, that the master uses a SSL certificate that contains the local FQDN (e.g. master.mycorp.intra).
In some scenarios the SSL certificate of the apache is replaced by a custom SSL certificate (e.g. let's encrypt) that contains only the public FQDN of the UCS master (e.g. www.mycorp.com).

The diagnosis module should check if the master (and/or dc backups) is accessible via HTTPS and uses a certificate that also provides the local FQDN at least as alternativeName.

Comment 1 Ingo Steuwer

2020-07-03 20:54:10 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.