9.2.1. Introduced in 7.3.1
The following regressions were introduced in Connext 7.3.1.
9.2.1.1. Core Libraries
9.2.1.1.1. Incorrect TypeSupport-to-JSON conversion for an empty structure with a non-empty parent
The JSON-formatted string for a DynamicData sample is malformed if the
sample has a base structure that is empty and the base structure has a parent
structure that is non-empty. For example, consider the following IDL:
struct Struct1 {
long x;
};
struct Struct2 : Struct1 {
};
struct Struct3 : Struct2 {
short y;
};
and the following Modern C++ code snippet:
DynamicData struct3_dd(dynamic_type<Struct3>::get());
std::string str = rti::topic::to_string(
struct3_dd,
PrintFormatProperty::Json());
The resulting str will look like {"x":0 "y":0}. The lack of a comma is
considered a JSON syntax error. In the fix for this issue, the str
looks like {"x":0, "y":0}.
Not fixed yet in a major release: May be fixed in a patch; see Regressions.
[RTI Issue ID CORE-17131]
9.2.1.2. Security Plugins
9.2.1.2.1. No re-authentication with 7.3.0 or below
The re-authentication mechanism described in Asymmetric Authentication Failure does not work when DomainParticipant P1 is using the Builtin Security Plugins 7.3.0 or below and DomainParticipant P2 is using version 7.3.1 or above. The change described in Authentication class_id now conforms to the value in the DDS Security 1.2 Specification introduces this problem; “DomainParticipants still propagate the DDS:Auth:PKI-DH:1.0 class_id to remote DomainParticipants from previous RTI releases” is not true for the Authentication Request message. If P1 does not have the fix for RTI Issue ID SEC-2473, then P1 generates the following error message, and re-authentication fails unrecoverably:
RTI_Security_Authentication_processAuthRequest:received unexpected identity token with class id different from DDS:Auth:PKI-DH:1.0+AuthReq and com.rti.sec.DDS:Auth:PKI-DH:1.0+AuthReq
Not fixed yet in a major release: May be fixed in a patch; see Regressions.
[RTI Issue ID SEC-3055]