Project

General

Profile

Actions

Bug #1390

closed

Invalid Certificates need better handling

Added by Greg Sutcliffe over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Some stupid people in my enterprise have got strange ideas on what an FQDN is...

They have managed to create hosts with certificate names like ".stsn.com" and ".ibahn.com" - of course, when Foreman tries to parse that, it gets nil for the hostname. We need to handle that better so that the Certificate Management page doesn't blow up when trying to render it.

Interestingly, if you revoke (but not clean) the offending cert, Foreman displayed the revoked certificate just fine.

Actions

Also available in: Atom PDF