View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008977CTT UA Scripts1 - Script Issuepublic2023-05-22 10:002024-02-01 17:02
ReporterV. Monfort Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version1.04.501 
Summary0008977: Security certificate validation 038: expects Bad_SecurityChecksFailed whereas Bad_CertificateRevoked is actually expected
Description

UACTT V1.04.11-01.00.502

As indicated in issue 0008968 the following text for Revocation Check needs to be removed from Part 4:
"If this check fails on the Server side, the error Bad_SecurityChecksFailed shall be reported back to the Client."

As consequence the expected status to be reported to the Client is Bad_CertificateRevoked instead of Bad_SecurityChecksFailed which is currently expected in UACTT script 038.js.

TagsNo tags attached.
Files Affected

Relationships

related to 0008968 closedRandy Armstrong 10000-004: Services Part 4 §6.1.3 should indicate that the error reported by the server to the client is Bad_SecurityChecksFailed for all steps 

Activities

Paul Hunkar

2023-05-26 14:54

administrator   ~0019433

wait for spec updates before fixing - but agree to fix

Alexander Allmendinger

2023-06-16 14:49

developer   ~0019501

Regarding this issue there have been multiple discussion in the Security and UA Working Groups. We will be waiting until all open spec issues are closed before updating the test cases one way or the other. Right now the expectation for the server is to return a Bad_SecurityChecksFailed.

V. Monfort

2023-10-12 07:23

reporter   ~0020135

Hello,
Since the spec issue has been closed with the choice not to change anything I guess you should close this ticket.

Note that the incoherence between the two columns in part 4 table 106 of the spec (Bad_SecurityChecksFailed missing in the Error column) will then remain.

Thanks and best regards.

Alexander Allmendinger

2024-01-25 13:59

developer   ~0020707

As discussed in the security WG there is no change required.

Paul Hunkar

2024-02-01 17:02

administrator   ~0020753

agree no change required

Issue History

Date Modified Username Field Change
2023-05-22 10:00 V. Monfort New Issue
2023-05-26 14:54 Paul Hunkar Assigned To => Paul Hunkar
2023-05-26 14:54 Paul Hunkar Status new => assigned
2023-05-26 14:54 Paul Hunkar Note Added: 0019433
2023-05-26 14:54 Paul Hunkar Relationship added related to 0008968
2023-06-16 14:49 Alexander Allmendinger Note Added: 0019501
2023-10-05 14:23 Paul Hunkar Assigned To Paul Hunkar =>
2023-10-12 07:23 V. Monfort Note Added: 0020135
2024-01-25 13:59 Alexander Allmendinger Assigned To => Alexander Allmendinger
2024-01-25 13:59 Alexander Allmendinger Status assigned => resolved
2024-01-25 13:59 Alexander Allmendinger Resolution open => no change required
2024-01-25 13:59 Alexander Allmendinger Note Added: 0020707
2024-02-01 17:02 Paul Hunkar Status resolved => closed
2024-02-01 17:02 Paul Hunkar Note Added: 0020753