View Issue Details

IDProjectCategoryView StatusLast Update
0003558Compliance Test Tool (CTT) Unified Architecture3 - Feature Requestpublic2018-07-31 17:42
ReporterNathan PocockAssigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.02.336.273 
Target Version1.04Fixed in Version1.03.340.368 
Summary0003558: Session Base Err-007 fails with secure connection
Description

<Background>
When 'Server Test/Secure Channel/MessageSecurityMode' is set to Sign or
SignAndEncrypt, test case of 'Session Services/Session Base/Test Cases'
which is invoked after Err-007.js fails within 'Run to first error'
procedures.
The attached fail-case.png shows the situation. I experience that
Err-010.js fails if Err-009.js is unchecked to test. And Err-009.js and
Err-010.js success if they are executed via 'Start Debug Run'.
And the error message is like 'Request handle sent is not match with the
request handle within response'.

The description of Err-007 is 'Over a non-secure channel; call
ActivateSession() specifying an empty ClientSignature.'. That is, this
test is for only case where 'Server Test/Secure
Channel/MessageSecurityMode' is None. And it looks like that no test is
done in case of Sign or SignAndEncrypt. So I commented out the
procedures for Sign or SignAndEncrypt as shown in success-case.png
(Please compare the script in sucess-case.png with fail-case.png). Then
the problem has gone as sucess-case.png shows.

TagsNo tags attached.
Attached Files
success-case.png (84,996 bytes)   
success-case.png (84,996 bytes)   
fail-case.png (68,221 bytes)   
fail-case.png (68,221 bytes)   
Files Affected

Activities

Alexander Allmendinger

2017-09-15 07:32

developer   ~0008454

Because we are pushing the CTT V1.03 to be released this issue is going to be deferred.

Alexander Allmendinger

2017-11-13 20:13

developer   ~0008703

Followed the suggestion of Thomas Merk and changed the else clause in order to run the test case like intended.

Paul Hunkar

2018-07-31 17:42

administrator   ~0009238

reviewed in CMP call

Issue History

Date Modified Username Field Change
2016-10-07 13:54 Nathan Pocock New Issue
2016-10-07 13:54 Nathan Pocock Status new => assigned
2016-10-07 13:54 Nathan Pocock Assigned To => Nathan Pocock
2016-10-07 13:54 Nathan Pocock File Added: success-case.png
2016-10-07 13:54 Nathan Pocock File Added: fail-case.png
2017-08-03 16:39 Paul Hunkar Assigned To Nathan Pocock => Alexander Allmendinger
2017-09-15 07:32 Alexander Allmendinger Note Added: 0008454
2017-09-15 07:32 Alexander Allmendinger Category Implementation Bug => Feature Request
2017-09-15 07:32 Alexander Allmendinger Target Version => 1.04
2017-11-13 20:13 Alexander Allmendinger Note Added: 0008703
2017-11-13 20:13 Alexander Allmendinger Status assigned => resolved
2017-11-13 20:13 Alexander Allmendinger Fixed in Version => 1.03.340.368
2017-11-13 20:13 Alexander Allmendinger Resolution open => fixed
2018-07-31 17:42 Paul Hunkar Note Added: 0009238
2018-07-31 17:42 Paul Hunkar Status resolved => closed
2019-01-28 14:14 Paul Hunkar Category Feature Request => 3 - Feature Request