Actions
Bug #18995
closed
Missing mandatory directive parameter doesn't fail policy generation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
It seems that at some point, we lost the check for mandatory parameters during policy generation (or perhaps we never had one - we at least have a `SaveDirectivesOnTechniqueCallback` but AFAIR it was only to update information saved in LDAP).
So, it means that if a new mandatory parameter is added, then the policy generation doesn't fail.
Updated by 
Updated by
Actions