Bug #12827: Fix cas access-log buffering

[ghost]

Description

Désactivation du buffering des access-logs de CAS

Contributeur

VAS (Vitam Accessible en Service)

[vitam-devops]

Checkmarx One – Scan Summary & Details – 1fab5762-4655-49b8-ab0b-a3a4bbf5da4b

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	CVE-2019-15599	Npm-tree-kill-1.2.1	Vulnerable Package
	CVE-2020-28502	Npm-xmlhttprequest-ssl-1.5.5	Vulnerable Package
	CVE-2020-36048	Npm-engine.io-3.2.1	Vulnerable Package
	CVE-2020-36049	Npm-socket.io-parser-3.2.0	Vulnerable Package
	CVE-2020-7660	Npm-serialize-javascript-1.9.1	Vulnerable Package
	CVE-2020-7788	Npm-ini-1.3.5	Vulnerable Package
	CVE-2021-31597	Npm-xmlhttprequest-ssl-1.5.5	Vulnerable Package
	CVE-2022-2421	Npm-socket.io-parser-3.2.0	Vulnerable Package
	CVE-2019-16769	Npm-serialize-javascript-1.9.1	Vulnerable Package
	CVE-2020-15366	Npm-ajv-6.10.0	Vulnerable Package
	CVE-2020-15366	Npm-ajv-5.5.2	Vulnerable Package
	CVE-2020-28481	Npm-socket.io-2.1.1	Vulnerable Package
	CVE-2020-7693	Npm-sockjs-0.3.19	Vulnerable Package
	CVE-2021-23364	Npm-browserslist-4.5.5	Vulnerable Package
	CVE-2022-21704	Npm-log4js-4.5.1	Vulnerable Package
	CVE-2022-41940	Npm-engine.io-3.2.1	Vulnerable Package
	Logging of Sensitive Data	/ansible.cfg: 2	To keep sensitive values out of logs, tasks that expose them need to be marked defining 'no_log' and setting to True
	Logging of Sensitive Data	/ansible.cfg: 1	To keep sensitive values out of logs, tasks that expose them need to be marked defining 'no_log' and setting to True
	Logging of Sensitive Data	/ansible.cfg: 2	To keep sensitive values out of logs, tasks that expose them need to be marked defining 'no_log' and setting to True