DDS-Security 1.0 FTF Avatar
  1. OMG Issue

DDSSEC_ — Value of HandshakeRequestMessageToken 1st property

  • Key: DDSSEC_-17
  • Legacy Issue Number: 19780
  • Status: closed  
  • Source: ZettaScale Technology ( Mr. Julien Enoch)
  • Summary:

    In table 31, the "properties" attribute is specified with 2 properties. The first is described as:
    "A property with name set to “dds.sec.identity” and value set to string containing the elements of the value attribute of the IdentityCredential, one character per element. Note that the octets in the IdentityCredential value were defined to hold
    characters resulting from a PEM encoding ( 9.3.2.1) so the value of the property is precisely those characters."

    In ยง9.3.2.1 the IdentityCredential is defined with 2 "values" attribute: binary_value1 and binary_value2.
    Which one shall be used as property value for HandshakeRequestMessageToken ? binary_value1 I guess, but it should be specified.

  • Reported: DDS-Security 1.0b1 — Mon, 8 Jun 2015 04:00 GMT
  • Disposition: Resolved — DDS-Security 1.0
  • Disposition Summary:

    Table 21 - Specify the use of the IdentityCredential binary_value1 in the properties

    Table 21 - "properties" row, "Attribute value" column. When describing the construction of the property name "dds.sec.identity" it mentions the use of the "value" attribute from the IdentityCredential. Instead of "value" it should say "binary_value1".

  • Updated: Tue, 12 Jul 2016 14:45 GMT