View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007499 | 10000-012: Discovery | Spec | public | 2021-12-26 14:23 | 2022-06-21 08:58 |
| Reporter | Alexander Allmendinger | Assigned To | Randy Armstrong | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 1.05.02 RC1 | ||||
| Summary | 0007499: Missing requirement to validate subjectName in CreateSigningRequest | ||||
| Description | There is no requirement in the CreateSigningRequest section which requires the application to validate the subjectName provided in the inputArguments. Only the Method Result Codes imply that this needs to be validated by defining Bad_InvalidArgument with "The certificateTypeId, certificateGroupId or subjectName is not valid." If this is really required, this requirement should be added to the definition above. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
The subject in the CSR may be ignored by the CertificateManager. The CertificateManager may udpate the subject to comply with policy requirements and to ensure global uniqueness. |
|
|
Agreed to changes in Munich F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-12-26 14:23 | Alexander Allmendinger | New Issue | |
| 2022-02-08 18:00 | Jim Luth | Assigned To | => Randy Armstrong |
| 2022-02-08 18:00 | Jim Luth | Status | new => assigned |
| 2022-06-20 11:33 | Randy Armstrong | Status | assigned => resolved |
| 2022-06-20 11:33 | Randy Armstrong | Resolution | open => fixed |
| 2022-06-20 11:33 | Randy Armstrong | Note Added: 0016864 | |
| 2022-06-21 08:58 | Jim Luth | Status | resolved => closed |
| 2022-06-21 08:58 | Jim Luth | Fixed in Version | => 1.05.02 RC1 |
| 2022-06-21 08:58 | Jim Luth | Note Added: 0016928 |
