View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005778Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2020-07-02 13:152021-04-29 15:31
ReporterBernd Edlinger Assigned ToAlexanderAllmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.03.341.396 
Fixed in Version1.03.341.397 
Summary0005778: Session Base/008.js script error
Description

I used UaCtt-1.3.341.396-x86_64.AppImage, the following happens:

Session Base/008.js
Error: Test.Execute() encounted an unexpected error:
message:buildUserNameIdentityToken(session = UaSessionClass(name = ""), username = 'User1', password = 'Pwd1', doNotAppendNonce
= false) at /home/ed/OPCToolboxV5/EmbeddedStack/Source/CTT/EmbeddedCtt/library/Base/identity.js:327
lineNumber:327
sourceId:140453729248576
fileName:/home/ed/OPCToolboxV5/EmbeddedStack/Source/CTT/EmbeddedCtt/library/Base/identity.js
name:TypeError

Backtrace: function:
file: .../library/Base/safeInvoke.js
line: 126
file: .../maintree/Session Services/Session Base/Test Cases/008.js
line: 39

I debugged a bit, and the last thing before the script crashes is here:
Base/identity.js line 326:
var status = cryptoProvider.asymmetricEncrypt( encodedPassword, gServerCapabilities.ServerCertificate.PublicKey, encryptedPassword );

this line jumps directly to the exception handler.

TagsNo tags attached.
Files Affected

Activities

Bernd Edlinger

2020-07-07 08:36

reporter   ~0012555

Last edited: 2020-07-07 08:37

The problem only happens when the following setting is done:
Server Test/Session
UserAuthenticationPolicy = 1

When I change that to 0 = Anonymous, no error happens.

Another possibly relevant setting we use is:
ServerTest/Secure Channel
MessageSecurityMode = SignAndEncrypt
RequestedSecurityPolicyUri = Basic256Sha256

Sebastian Allmendinger

2021-04-13 14:07

developer   ~0014195

The issue is neither reproducible with current version (.398) nor with the released version (.396) for Windows.
The issue seems to be related to MantisId=5661. There was a commit with an additional fix for this issue shortly before the release. It looks like this commit was only part of the windows version and was missing in the version for linux.
The issue should already be resolved in the most recent released version (.398) for both platforms.

Paul Hunkar

2021-04-29 15:31

administrator   ~0014283

Reviewed in CMP call. Agreed to changes and closed

Issue History

Date Modified Username Field Change
2020-07-02 13:15 Bernd Edlinger New Issue
2020-07-07 08:36 Bernd Edlinger Note Added: 0012555
2020-07-07 08:36 Bernd Edlinger Note Edited: 0012555
2020-07-07 08:37 Bernd Edlinger Note Edited: 0012555
2020-07-10 17:21 Paul Hunkar Assigned To => AlexanderAllmendinger
2020-07-10 17:21 Paul Hunkar Status new => assigned
2021-04-13 14:07 Sebastian Allmendinger Note Added: 0014195
2021-04-13 14:08 Sebastian Allmendinger Status assigned => resolved
2021-04-13 14:08 Sebastian Allmendinger Resolution open => fixed
2021-04-13 14:08 Sebastian Allmendinger Fixed in Version => 1.03.341.397
2021-04-29 15:31 Paul Hunkar Status resolved => closed
2021-04-29 15:31 Paul Hunkar Note Added: 0014283