Details
-
Sub-task
-
Resolution: Unresolved
-
Major
-
None
-
None
Description
Part of parent issue whereby slaves can ignore missing RBAC constraint resources for write requests coming from the DC.
If the DC sent the request, then the address is ok overall. So if it's missing on the slave that means the slave doesn't have that constraint registered and doesn't need to handle the op.
This fix could possibly be backported to the 2.1.x and to EAP 6.4.x in lieu of adding transformers as part of the parent issue. In the case of 2.1.x it also allows slaves to ignore the related extension even if the code for it is present (which is only a minor benefit.)