Setting the customer validation and hmac validation on by
default also moving customer validation into its own function
so it can be tested more easily and extending the tests
to showcase the logic the work was started by @ivanayov
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
For derek users with authentication turned off if they move to the newest version, they should explicitly set the validate_customers: 0/false and validate_hmac:0/false
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Setting the customer validation and hmac validation on by default also moving customer validation into its own function so it can be tested more easily and extending the tests to showcase the logic the work was started by @ivanayov
Signed-off-by: Martin Dekov (VMware) mdekov@vmware.com
Description
This adds more secure experience for the user so the hmac and security validation should now be turned off intentionally with explicit
false
or0
Motivation and Context
Actually part of #316 issue in OpenFaaS Cloud
How Has This Been Tested?
Unit tests
Types of changes
For derek users with authentication turned off if they move to the newest version, they should explicitly set the
validate_customers: 0/false
andvalidate_hmac:0/false
Checklist:
git commit -s