Fixing Communication between LabVIEW Security Shapes Demo Example and RTI Shapes Demo using Security

1 post / 0 new
Offline
Last seen: 6 months 3 weeks ago
Joined: 04/23/2014
Posts: 45
Fixing Communication between LabVIEW Security Shapes Demo Example and RTI Shapes Demo using Security
AttachmentSize
Image icon secure_shapes_communication.png78.09 KB

Hello everybody,

Issues when communicating the LabVIEW Security Shapes Demo example and the RTI Shapes Demo using Security may be caused due to a mismatch in the certificates between both applications, which have to be the same ones. Otherwise the signature won’t match and both application don’t rely on each other.

This may happen when the version of the both Shapes Demo is different. So, different versions of RTI Shapes Demo with Security can be used to communicate with LabVIEW Security Shapes Demo as long as they are using the same certificate files.

A simply way of fixing this is just to copy the RTI Shapes Demo certificates into the LabVIEW Security Shapes Demo example folder. These paths will be based on the RTI Shapes Demo installation folder. The files that we need to copy are:

  • resource\cert\RTI_SHAPES_DEMO_CA_CERT.pem
  • resource\cert\RTI_SHAPES_DEMO_PEER_2_KEY.pem
  • resource\cert\RTI_SHAPES_DEMO_PEER_1_CERT.pem
  • resource\cert\RTI_SHAPES_DEMO_PEER_3_CERT.pem
  • resource\cert\RTI_SHAPES_DEMO_PEER_1_KEY.pem
  • resource\cert\RTI_SHAPES_DEMO_PEER_3_KEY.pem
  • resource\cert\RTI_SHAPES_DEMO_PEER_2_CERT.pem    
  • resource\xml\signed\RTI_SHAPES_DEMO_GOVERNANCE_MAX.p7s
  • resource\xml\signed\RTI_SHAPES_DEMO_GOVERNANCE_MIN.p7s
  • resource\xml\signed\RTI_SHAPES_DEMO_PERMISSIONS.p7s

We have to replace the certificates shipped with LabVIEW under:

  • <LabVIEW installation path>\examples\RTI DDS Toolkit\SecurityShapesDemo\cert\

Then, the LabVIEW Security Shapes Demo will load the same files that the RTI Shapes Demo and the communication will work again (as long as it is allowed by your security permissions :D).