The CTT should be updated to run these test using a secure endpoint (not none)

The CTT should nevertheless be able to run this test successfully on servers that only have a none endpoint

The test scripts in the Conformance Group Base Information TypeSystem validate general expectations/rules for TypeDefinitions and Instances of these Types.

Because they are not intended to validate the actual values (or any access rights), there is already a suppression of any bad status when reading the values of attributes implemented.
But in some cases, an evaluation of the StatusCode was missing and the test script continued with the validation even if the value is not available.
This happened for example for the InputArguments of methods. In the case of the reporters server, the CTT received a bad result when reading the InputArguments of a security related method and then validated a not existing value against the expectation that it must be an array. This - of course - failed.

The test scripts have been updated to skip the validation if it receives a bad result.

The CTT uses the Default SecureChannel and Authentification that can be configured in the settings of the CTT for these tests. It is recommended and also part of the certification tests to run the CTT against secure and insecure endpoints as default.