Bug 50436 – Make wildcard certificates available for hosts that request it

Bug 50436 - Make wildcard certificates available for hosts that request it


Summary:	Make wildcard certificates available for hosts that request it

Status:	NEW

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

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Dirk Wiesenthal
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:	54697
Blocks:	45115 50445
	Show dependency tree / graph

Reported:	2019-10-30 13:50 CET by Dirk Wiesenthal
Modified:	2022-04-28 08:41 CEST (History)
CC List:	5 users (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):	External feedback
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 Dirk Wiesenthal

2019-10-30 13:50:42 CET

Wildcard certificates below the internal name of a computer ("*.member5.intranet.mydomain.com) should be possible.

The idea is that a host "requests the certificate", the DC Master creates it, the host downloads it.

+++ This bug was initially created as a clone of Bug #45115 +++

We should think about making the app available via appid.domain (not only fqdn/app)