Cause: PortalSetupService had a bug when working with multiple containers at same time and there was a configuration missing in sample-portal.
Consequence: root user could not sign in into sample-portal container, although one has set the root password using the web form shown on the first request after the installation. Note that this problem has not occurred when the root password was set using bin/setup-portal.sh script before the first start of the portal.
Fix: In Portal, the PortalSetupService was fixed to work with multiple containers and the missing configuration was added to sample portal.
Result: Now, the root password initialization is shown for every portal container separately and root user can sign in into all portal containers.