-
Key: DDSSEC11-16
-
Status: closed
-
Source: Real-Time Innovations ( Dr. Gerardo Pardo-Castellote, Ph.D.)
-
Summary:
Section 8.8.7.2 (AccessControl behavior with discovered endpoints from Authenticated DomainParticipant) and Figure 26 there show the operations on the AccessControl plugin that are called as a result of discovering a remote entity.
These sequence diagrams and Figure show when check_remote_datawriter and check_remote_datareader are called but do not mention the calls to check_local_datareader_match and check_local_datawriter_match
The calls to these operations should be added to the sequence diagram and descriptive text.
-
Reported: DDS-SECURITY 1.0 — Tue, 24 May 2016 01:46 GMT
-
Disposition: Resolved — DDS-SECURITY 1.1
-
Disposition Summary:
Improve AccessControl interface wrt check_local and check_remote operations
It is necessary to separate the security attributes into two constructs : TopicSecurityAttributes and EndpointSecurityAttributes. These inform the middleware which security operations must be invoked.
-
Updated: Tue, 19 Dec 2017 20:03 GMT
-
Attachments:
- Figure10_AccessControl_i122_i16.emf 105 kB ()
- Figure23_DDSSecurity-LocalParticipantAccess_i16.emf 101 kB ()
- Figure25_DDSSecurity-RemoteEndpoint-UnprotectedAccess_i16.emf 52 kB ()
- Figure26_DDSSecurity-RemoteEndpoint-ProtectedAccess_i16.emf 66 kB ()
- dds_security_plugins_spis_ballot5_i33_i66_i16.idl 33 kB ()
DDSSEC11 — AccessControl behavior does not show check_local_datawriter/reader_match operations
- Key: DDSSEC11-16
- OMG Task Force: DDS Security 1.1 RTF