Actions
Bug #15344
closedAPI for node key management
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
The API endpoints is POST .../nodes/uuid with properties agentKey a json with the following fields:
- value: the PEM string of the key/certificate. The type is automatically infered from the PEM (ie either certificate or publicKey)
- status: verified status of the key, by default the key is
certified
if the key is given. Accepted value =undefined
,certified
The API should also accept non JSON POST like that:
POST .../nodes/uuid -d "agentKey.status=reset"
to reset the certificate status,POST .../nodes/uuid/ -d "agentKey.value=---- BEGIN CERTIFICATE ...."
to set a new key.
And if you want to do fancy things: POST .../nodes/uuid -d '{ "agentKey": { "status":"undefined", "value":"--- BEGIN CERTIFICATE ..." }
Updated by François ARMAND over 5 years ago
- Status changed from New to In progress
Updated by Alexis Mousset over 5 years ago
- Related to Bug #14871: Rudder command to reset agent key/certificate added
Updated by François ARMAND over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2349
Updated by François ARMAND over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|24a2123a571cd1548567989f2dec398e3d51eae2.
Updated by Vincent MEMBRÉ about 5 years ago
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
Actions