- 
                            Key: DDSSEC11-31
- 
                            Status: closed
- 
                            Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
- 
                            Summary:The spec defines the retcode VALIDATION_OK_FINAL_MESSAGE in Table 19 and in http://www.omg.org/spec/DDS-SECURITY/20160303/dds_security_plugin_spis.idl. However, there are multiple uses of wrong VALIDATION_OK_WITH_FINAL_MESSAGE . 
- 
                            Reported: DDS-SECURITY 1.0 — Wed, 5 Oct 2016 13:34 GMT
- 
                            Disposition: Resolved — DDS-SECURITY 1.1
- 
                            Disposition Summary:*Replace VALIDATION_OK_WITH_FINAL_MESSAGE Occurrences with VALIDATION_OK_FINAL_MESSAGE * Replace the following VALIDATION_OK_WITH_FINAL_MESSAGE with VALIDATION_OK_FINAL_MESSAGE: - In Figure 9 – Authentication plugin interaction state machine.
- In Figure 22 – Authentication sequence diagram with discovered DomainParticipant.
- In 8.8.2.2 Behavior when allow_unauthenticated_participants is set to FALSE, step 11.
- In Table 41 – Actions undertaken by the operations of the builtin Authentication plugin:
	- In "process_handshake on a handshake_handle created bybegin_handshake_request"
- In "get_shared_secret"
- In "get_authenticated_peer_credential_token"
 
 
- 
                            Updated: Tue, 19 Dec 2017 20:03 GMT
- 
                            Attachments:- AuthBehavior.emf 115 kB ()
- DDSSecurity-RemoteParticipant.emf 96 kB ()
 
DDSSEC11 — Wrong ValidationResult_t VALIDATION_OK_WITH_FINAL_MESSAGE Used In Multiple Places
- Key: DDSSEC11-31
- OMG Task Force: DDS Security 1.1 RTF