Prevent Bamboo from starting as a different user account

Bamboo may allow inadvertently users to start using any user accounts. This situation may lead to files being written as a different user, often with root or Administrator, with will also leave the application running with administrative privileges, which could lead to potential security risks and operational issues.

To mitigate this, I propose the following enhancements to the Bamboo startup process:

• User Account Verification: Bamboo should include a verification process upon startup to check the user account currently running the application. This will involve comparing the current system user with a predefined service user. If these don't match, the application should prevent the startup process from continuing, avoiding the creation of files under the wrong user account.
• User Account Switch: In cases where it is necessary to modify the service user account running the application due to migration, a switch must be used to inform Bamboo of the intended change. This switch could be a Java system property such as `-Dbamboo.update.service.user=true` that can be set temporarily to allow the service user to be changed in the configuration file and later get removed to restore the service user checks.

Implementing such features will help ensure that Bamboo is always run under the correct user account, reducing potential security risks and operational issues. They will also provide a straightforward means for administrators to switch user accounts when necessary.