You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we add a topic in deny_rule using governance.xml and permissions.xml, we should cannot make topic given DomainParticipant::create_topic function.
Current behavior
When we add a topic in deny_rule using governance.xml and permissions.xml, DomainParticipant::create_topic are just worked even topics are in deny_rule.
The check_rule function which checks rule of topis only runs on these functions: Permissions::check_create_datawriter, Permissions::check_create_datareader, Permissions::check_remote_datawriter, Permissions::check_remote_datareader, but not on topic.
Is there an already existing issue for this?
Expected behavior
When we add a topic in
deny_rule
using governance.xml and permissions.xml, we should cannot make topic givenDomainParticipant::create_topic
function.Current behavior
When we add a topic in
deny_rule
using governance.xml and permissions.xml,DomainParticipant::create_topic
are just worked even topics are indeny_rule
.Fast-DDS/src/cpp/security/accesscontrol/Permissions.cpp
Lines 153 to 162 in 6eb1170
The
check_rule
function which checks rule of topis only runs on these functions:Permissions::check_create_datawriter
,Permissions::check_create_datareader
,Permissions::check_remote_datawriter
,Permissions::check_remote_datareader
, but not on topic.Steps to reproduce
FastDDS-api-poc.zip
We cannot make topic, but PoC publisher successfully make topic and running 10 samples.
Fast DDS version/commit
Platform/Architecture
Other. Please specify in Additional context section.
Transport layer
UDPv4
Additional context
We should check rules when creating a topic.
Relevant sections of DDS Security v1.1 include:
8.4.2.9.6 Operation: check_create_topic
8.8.5 AccessControl behavior with local domain entity creation
9.4.3 DDS:Access:Permissions plugin behavior
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response
The text was updated successfully, but these errors were encountered: