Prompting for the Master Password at Server Initialization

The configpassman.cnf file provides properties that you can use to prompt for the master password at server initialization.

Use these properties only if you want Integration Server to prompt for the password at server initialization (that is, you specified false for master.password.storeInFile.

Keep the following information in mind when deciding whether to configure Integration Server to prompt for the master password at server initialization:

To prompt for the master password at server initialization, the master.password.storeInFile property must be set to false.

Integration Server runs in headless mode as controlled by the following property in custom_wrapper.conf: wrapper.java.additional.205=-Djava.awt.headless=true

If you want Integration Server to prompt for the master password during server initialization, you must edit custom_wrapper.conf to have the following: wrapper.java.additional.205=-Djava.awt.headless=false

For more information about editing the custom_wrapper.conf file, see Changing Settings in the Configuration File custom_wrapper.conf.

Note: To run Microservices Runtime in headless mode, edit the JAVA_CUSTOM_OPTS property in Integration Server_directory /bin/setenv.bat(sh) to include the following property: java.awt.headless=true set for the For information about passing Java system properties to Microservices Runtime, see .

You cannot configure Integration Serverto prompt for the master password at server initialization if:

Integration Server runs as a Windows service.

Integration Server runs as a background application on UNIX.

If you do not want Integration Server to prompt for the password at server initialization, make sure to comment out the following properties in the configpassman.cnf file: master.password.field.useGUIand master.password.field.attemptsLimit.

To configure Integration Server to prompt for master password at server initialization

1. Use a text editor to open the following file:

Integration Server_directory /instances/instance_name/config/configPassman.cnf

2. Make sure master.password.field.useGUI and master.password.field.attemptsLimit are not commented out. If the parameters do not exist in the file, add them.

3. Set the properties as described in the following table.

Property	Description
master.password.storeInFile	Controls whether Integration Server stores the master password in a file. Set to false.
master.password.field.usgeGUI	Specifies where Integration Server prompts for the master password. Set to true to prompt for the password in a popup window. If you choose this method, you can start Integration Server from the Windows start menu. Set to false to prompt for the password on the server console. If you choose this method, you cannot start Integration Server from the Windows start menu. The default is true.
master.password.field.attemptsLimit	Indicates the number of unsuccessful login attempts permitted before Integration Server rejects the request. The default is 3.

4. Save and close the configPassman.cnf file.