View Issue Details

IDProjectCategoryView StatusLast Update
0007678CTT UA Scripts1 - Script Issuepublic2022-10-12 16:39
ReporterMark Clemens Assigned ToAlexander Allmendinger  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Summary0007678: Script error when OPC UA Server uses null for the SecurityTokenPolicyUri and both Sign and Sign & Encrypt are supported
Description

Test 015.js in Security\Security User Name and Password\Test Cases fails with a false-positive duplicate PolicyId detection, when the OPC UA Server uses null for the SecurityTokenPolicyUri for the UserTokenPolicy and the OPC UA Server has Endpoints for both sign and sign&encrypt for the same SecurityPolicyUri, which would be legit.

The issue can be resolved if in the initialize.js a variable epSecureSign is defined and in line 54 also the endpoints that offer only sign are searched, similar to the function in line 53.

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2022-02-03 16:35

administrator   ~0015915

Push to later release

Alexander Allmendinger

2022-08-04 16:53

developer   ~0017294

Could you please provide the EndpointDescriptions of your server? E.g. make a screenshot of the Server Diagnostics View in UA Expert for the different endpoints.

We are not sure about the exact configuration of the server which would cause this problem.

Alexander Allmendinger

2022-09-08 13:20

developer   ~0017565

We can only reproduce the issue when having the endpoints configured to define the same UserToken PolicyID on sign and sign&encrypt but in one case no SecurityPolicyUri is defined and in the other it is defined. e.g.:

Secure Entpoint with SecurityPolicy Basic256Sha256 and the field in the UserToken for the uri is empty

  • Secure Entpoint with SecurityPolicyUri AesXXX and the field in the UserToken for the uri is Basic256Sha256

In this case it would result in the same user token but the definition is different and therefore correctly flagged as issue by the script. In other scenarios we have not been able to reproduce the issue. Because the server of the reporter is now fixed and doesn't run in this behavior any more, no change is required.

Paul Hunkar

2022-10-12 16:39

administrator   ~0018012

reviewed issue in call, agreed to no fix,closed issue

Issue History

Date Modified Username Field Change
2022-01-28 14:20 Mark Clemens New Issue
2022-02-03 16:35 Paul Hunkar Assigned To => Alexander Allmendinger
2022-02-03 16:35 Paul Hunkar Status new => assigned
2022-02-03 16:35 Paul Hunkar Status assigned => acknowledged
2022-02-03 16:35 Paul Hunkar Note Added: 0015915
2022-08-04 16:53 Alexander Allmendinger Status acknowledged => feedback
2022-08-04 16:53 Alexander Allmendinger Note Added: 0017294
2022-08-25 03:09 Paul Hunkar Project Compliance Test Tool (CTT) Unified Architecture => CTT UA Scripts
2022-09-08 13:20 Alexander Allmendinger Status feedback => resolved
2022-09-08 13:20 Alexander Allmendinger Resolution open => no change required
2022-09-08 13:20 Alexander Allmendinger Note Added: 0017565
2022-10-12 16:39 Paul Hunkar Status resolved => closed
2022-10-12 16:39 Paul Hunkar Note Added: 0018012