Project

General

Profile

Actions

Bug #13817

closed

ENC smart proxy validation fails

Added by Matthew Ceroni almost 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Security
Target version:
Fixed in Releases:
Found in Releases:

Description

Using latest nightly and encountered the following error: No smart proxy server found on [] and is not in trusted_puppetmaster_hosts

As you can see it wasn't listing the connecting smart proxy / host. Dug into the code and found the following section of code:


if certificate.subject_alternative_names
request_hosts += certificate.subject_alternative_names
elsif certificate.subject
request_hosts << certificate.subject
end

Testing of certificate.subject_alternative_names always evaluates to true even when no SAN. This results in request_hosts to be empty and authentication of the request fails.


Related issues 1 (0 open1 closed)

Related to Foreman - Feature #12127: Foreman should verify x509 subject alternative names when authenticating a smart proxyClosedTimo Goebel10/09/2015Actions
Actions

Also available in: Atom PDF