Bug 50855 – Failed app installation when using wildcard certificate

Bug 50855 - Failed app installation when using wildcard certificate


Summary:	Failed app installation when using wildcard certificate

Status:	RESOLVED FIXED

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 major (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:	App Center maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-02-26 13:06 CET by Marc Schwarz
Modified:	2020-04-02 11:19 CEST (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	1: Will affect a very few 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.057
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2020010921000717
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 Marc Schwarz

2020-02-26 13:06:07 CET

There is a problem when installing apps on UCS subsystems due to the use of a wild card certificate (*.local.company.de).
However, the app center searches for the host name that is known within the domain, for example for cert "slave" and not slave.local.company.de
Is there a technical reason, that the FDQN is not used? If not: Would there be anything else against using the FDQN instead of the host name when querying so that the installation of apps on the UCS subsystems is possible?

Comment 1 Dirk Wiesenthal

2020-02-26 13:11:11 CET

When does this happen? When trying to install an App on "slave" while the user is logged in UMC on "master" ("global app center")?

Comment 2 Dirk Wiesenthal

2020-02-26 13:12:13 CET

If so, this would be a duplicate of Bug#50770, right?

Comment 3 Marc Schwarz

2020-02-26 13:13:25 CET

(In reply to Dirk Wiesenthal from comment #2)
> If so, this would be a duplicate of Bug#50770, right?

yes, same issue. Sorry for the duplicate!

Comment 4 Dirk Wiesenthal

2020-02-26 13:13:55 CET


*** This bug has been marked as a duplicate of bug 50770 ***