Bug #10852: Node key display differences - Rudder - Issue Tracker

Actions

Copy link

Bug #10852

closed

Node key display differences

Added by Florian Heigl over 7 years ago. Updated about 7 years ago.

Status:

Released

Priority:

N/A

Assignee:

Vincent MEMBRÉ

Category:

Web - UI & UX

Target version:

4.1.7

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Technique editor | Rudder settings

Effort required:

Very Small

Priority:

Name check:

Fix check:

Regression:

Description

Hi,

in "rudder agent info" we're shown the key hash as per cf-keys.
In the web interface we instead see the key as per the ppkeys/localhost.pub file.

Those infos cannot be compared and rudder should display the same thing in both places.

Actions

Copy link

Updated by François ARMAND over 7 years ago

Target version set to 3.1.21
Severity set to Minor - inconvenience | misleading | easy workaround
User visibility set to Operational - other Techniques | Technique editor | Rudder settings
Effort required set to Very Small

So, the best solution would be to also display the cfkey hash in the webapp.

It is given in 4.1, and harder in 3.1 (because in 4.1, we already have everything needed to calculate the CFEngine key hash, and it would be quite some code/dependencies to backport to 3.1 - but it must be checked).

Actions

Copy link

Updated by François ARMAND over 7 years ago

Priority changed from 0 to 35

Actions

Copy link

Updated by François ARMAND over 7 years ago

Target version changed from 3.1.21 to 4.0.7

So, it is doable in 4.0 and 4.1 trivially: just display the NodeInfo.cfengineKeyHash property in the UI, in node details "Display Node key" and updating the text to:

Display Node key:
Public Key:
-----BEGIN RSA PUBLIC KEY-----
.....
-----END RSA PUBLIC KEY-----

CFEngine Key Hash:
here-the-result-of-NodeInfo.cfengineKeyHash

Actions

Copy link