Project

General

Custom queries

Profile

Actions
Copy link

Refactor #15765

open

Improve client identification

Added by Shlomi Zadok almost 9 years ago. Updated over 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Branch:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Currently we use Katello or puppet certificates to identify the host (name / fqdn / uuid)
Those are subject to constantly change. We should figure how to identify the host from foreman_scap_client -> proxy -> foreman

Actions
Copy link
 #1

Updated by Marek Hulán over 8 years ago

What identification do you mean? On Foreman side we could use host id, it could be stored in /etc/foreman_scap_client/config.yml which is normally generated by puppet. If we need to identify it on smart proxy side because of authentication then certs are the only option I can think of without need for further query to Foreman.

Actions
Copy link

Also available in: Atom PDF