22 secured validation

[KaioKei]

Related Issue

22 Platform validation use resolver for ES security

How was it tested ?

1. Use a fresh 6.0.2 punchplatform deployer archive
2. Generate security configurations then deploy :

# fresh installation
make clean
make install
source activate.sh
# Mount vms and generate configurations
punchbox --config configurations/complete_punch_32G.json \
        --security
        --punch-conf <path_to_your_punchplatform_config_folder> \
        --deployer <path_to_your_punchplatform_deployer_zip> \
        --generate-vagrantfile \
        --start-vagrant
source activate 
punchplatform-deployer.sh --generate-platform-config --templates-dir punch/platform_template/ --model punch/build/model.json
# copy conf inside the shared folders
cp $PUNCHPLATFORM_CONF_DIR/punchplatform.properties $PUNCHBOX_DIR/punch/build/pp-conf
# deploy
punchplatform-deployer.sh deploy -u vagrant

3. Launch validation on server 1:

pp-conf/check_platform.sh

4. Verify that the validation ended well and check in Kibana the results of aggregations and validations

Author's checklist (You)

Before submitting merge request:

• [x] Resolve existing conflicts with a merge from the targeted branch into yours
• [x] Proceed to the tests
• [x] Check that the documentation explains these changes

After success review :

• [x] Push your branch
• [x] Assign and inform a reviewer

Reviewer's checklist (Reviewer)

• [ ] Technical review with the author
• [ ] Proceed to the tests
• [ ] Check that the documentation explains these changes
• [ ] Review and tests are done
• [ ] Inform the autor that the rieview is validated. The autor must be the one to merge its branch into the targeted one and push