Closed
Bug 1577343
Opened 6 years ago
Closed 6 years ago
Install Authenticode dep key in Staging Autograph and configure for Autograph
Categories
(Cloud Services :: Operations: Autograph, task)
Cloud Services
Operations: Autograph
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: u581815)
References
Details
Attachments
(1 file)
|
1.49 KB,
text/plain
|
Details |
No description provided.
Added to staging.
Command: findKey -l 201908_Authenticode_dep
Total number of keys present: 2
Number of matching keys from start index 0::1
Handles of matching keys:
524363, 524365
Cluster Error Status
Node id 2 and err state 0x00000000 : HSM Return: SUCCESS
Cfm3FindKey returned: 0x00 : HSM Return: SUCCESS
Command: getKeyInfo -k 524363
Cfm3GetKey returned: 0x00 : HSM Return: SUCCESS
Owned by user: 13
Shared with following 1 user(s):
9
Summary: Install Authenticode dep key in Staging Autograph → Install Authenticode dep key in Staging Autograph and configure for Autograph
Done:
- Created new key owner
Command: listUsers
Number Of Users Found: 13
Index User ID User Type User Name MofnPubKey LoginFailureCnt 2FA
...
13 13 CU ko_authenticode NO 0 NO
- Loaded in HSM, ready for configuration.
- updated docs
Remaining:
- update staging config for dep key
- deploy staging config
Assignee: hwine → gguthe
Config updated and deployed from the config train-3 branch with stack #235
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•