9327a33 Ticket 50727 - correct mistaken options in filter validation patch

Authored and Committed by firstyear 4 years ago
    Ticket 50727 - correct mistaken options in filter validation patch
    
    Bug Description: Because William of the past missed (forgot) to make
    some agreed upon changes, we shipped the feature for filter validation
    in a state that was a bit unclear for users.
    
    Fix Description: Fix the options to now be clearer in what is
    expected/demaned from admins. We now have 4 possible states for
    the value of the config:
    
    * reject-invalid  (prev on)
    * process-safe  (prev warn)
    * warn-invalid (new!)
    * off (prev off)
    
    These behave as:
    
    * reject-invalid - reject queries that contain unknown attributes
    * process-safe - log a notes=F that an attr is missing, and idl_alloc(0)
      the missing attribute for RFC4511 compliance.
    * warn-invalid - log a notes=F that an attr is missing, and process
      as ALLIDS (the legacy behaviour)
    * off - process as ALLIDs (the legacy behaviour)
    
    The default is "process-safe".
    
    https://pagure.io/389-ds-base/issue/50727
    
    Author: William Brown <william@blackhats.net.au>
    
    Review by: tbordaz, lkrispen (thanks)
    
        
file modified
+51 -33
file modified
+19 -7
file modified
+11 -10