View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000750010000-012: DiscoverySpecpublic2021-12-26 14:302022-06-21 10:13
ReporterAlexander Allmendinger Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version1.05.02 RC1 
Summary0007500: Method result codes of CreateSigningRequest is missing further validations
Description

According to the definition of the Signature of CreateSigningRequest it is required to specify a nonce when setting the regeneratePrivateKey to TRUE. But the Method Result Codes is not describing this scenario. So the to be returned error code is not clear.
Either the definition of Bad_InvalidArgument should not list any validation and should be defined as "One of the InputArguments is not valid" or it should list all required validations "One of more of the InputArguments certificateTypeId, certificateGroupId, subjectName or nonce is not valid."

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Alexander Allmendinger

2022-01-14 16:41

developer   ~0015719

Another question which was raised was, what does the server need to do if CreateSigningRequest is being called multiple times and regeneratePrivateKey is set and UpdateCertificate is not being called? Does it need to store all generated privateKeys? Is the new privateKey overwriting the earlier one? Does it need to search all generated PrivateKeys to find the correct one for the certificate in UpdateCertificate?

Randy Armstrong

2022-06-20 11:45

administrator   ~0016867

Last edited: 2022-06-21 10:13

State requirements for lifetime of key pairs and expanded error codes in 7.8.7.

Jim Luth

2022-06-21 10:13

administrator   ~0016933

Agreed to changes edited in Munich F2F.

Issue History

Date Modified Username Field Change
2021-12-26 14:30 Alexander Allmendinger New Issue
2022-01-14 16:41 Alexander Allmendinger Note Added: 0015719
2022-02-08 17:44 Jim Luth Assigned To => Randy Armstrong
2022-02-08 17:44 Jim Luth Status new => assigned
2022-06-20 11:45 Randy Armstrong Status assigned => resolved
2022-06-20 11:45 Randy Armstrong Resolution open => fixed
2022-06-20 11:45 Randy Armstrong Note Added: 0016867
2022-06-21 10:13 Randy Armstrong Note Edited: 0016867
2022-06-21 10:13 Jim Luth Status resolved => closed
2022-06-21 10:13 Jim Luth Fixed in Version => 1.05.02 RC1
2022-06-21 10:13 Jim Luth Note Added: 0016933