According to Kibana security folks, it does not make any difference to use unique cookie for individual user (tcp connection), unless we test Kibana. Since I saw instability during running 100+ concurrent session creating, this PR limits it to 1 per scalability journey run.
I also updated other existing journeys to use generated session cookie instead of login api call.
Checklist
Delete any items that are not applicable to this PR.
Summary
According to Kibana security folks, it does not make any difference to use unique cookie for individual user (tcp connection), unless we test Kibana. Since I saw instability during running 100+ concurrent session creating, this PR limits it to 1 per scalability journey run.
I also updated other existing journeys to use generated session cookie instead of login api call.
Checklist
Delete any items that are not applicable to this PR.