Configuring app passwords in web applications and servlets

The newly generated passwords must be transferred to the configuration for the relevant web applications and servlets. This can be achieved in various ways.

Via the web.xml file: In the case of FirstSpirit web applications, the app passwords can be configured in the web.xml file of the relevant web application using the firstspirit.password parameter, e.g.:

<!--  App Password for server connection. Not set = use default password   -->
<context-param>
  <param-name>firstspirit.password</param-name>
  <param-value>uNue gFTh pxtv D23C</param-value>
</context-param>

Once the web.xml file has been edited, the web applications must be restarted in order for the changes to take effect.

Via the system environment: Depending on the operating system, the app passwords can be configured directly on the application server using parameters that are specific to the operating system.

In a Windows environment (for example) via the following call:                                           
set FIRSTSPIRIT_PASSWORD=uNuegFThpxtvD23C  

In a Linux environment via the following call:                        
export FIRSTSPIRIT_PASSWORD=uNuegFThpxtvD23C

Via the Java environment: As a -D property using:            
-Dfirstspirit.password=uNuegFThpxtvD23C

Via the fs-wrapper.conf file (for the “Jetty Web Server” only): For the “Jetty Web Server”, the app passwords can be configured via Java properties within the file fs-wrapper.conf, e.g.:
wrapper.java.additional.5=-Dfirstspirit.password=uNuegFThpxtvD23C

If an empty string is passed instead of a value or if the parameter is not configured, authentication is always performed using the default password. However, this is only possible if the default password is enabled.

If the password is passed in the form of system or Java parameters, it is not allowed to contain any white spaces.

Via the servlet configuration: For specific applications, configuration can also be performed using servlet context parameters (in the web.xml file).

Evaluation order: The following evaluation order applies here (from highest priority to lowest priority):

1. Configuration of the parameter via the Java environment
2. Configuration of the parameter via the system environment         
3. Configuration of the parameter via the web.xml file