Configuring the spiuser password for Commerce+ Kubernetes Deployment

Setting the spiuser Password in Docker Images

During Commerce+ Kubernetes deployment, all containers must use the spiuser for inter-component communication, and there is no alternative user for this purpose.

The spiuser password is needed for:

• API calls between servers, such as:
  • Store server → Search server
  • Customization server → Transaction server
  • Transaction server → Customization server
  • Search server → Transaction and Customization servers

If the password is not set correctly or is mismatched, the servers will not be able to make the required API calls and won’t function together properly.

Procedure to Set the spiuser Password

1. Log on to the dedicated server that is hosting the Utility server Docker container.
2. Enter the Utility server Docker container. For example,

   docker exec -it utility_container_name bash

3. Navigate to the /opt/CommerceUtilities/bin/ directory.For example,

   cd /opt/CommerceUtilities/bin/

4. Encrypt the spiuser password: Run the following command to encrypt the spiuser password.

   ./wcs_encrypt.sh plain_text_spiuser_password

   Save the plain text password in a text file because you'll need it later.

5. Get the salt value for the spiuser password from the database:

   select salt from userreg where logonid='spiuser';

   If the result is NULL, set the salt with:

   update userreg set salt='salt' where logonid='spiuser';

   Salt should be a random string of 12 alphanumeric characters.

   For example, m83u229zjsrv.

6. Encrypt the salted password with the merchant key: Run the following command:

   ./wcs_password.sh plain_text_spiuser_password salt unencrypted_merchantKey_value

   If needed, you can use the -k option to encrypt the password without needing the merchant key.

7. Store the encrypted password in the database: Update the encrypted password through the command line based on the database solution that you are using.
   1. For DB2:

      update userreg set logonpassword=x'encrypted_hexadecimal_output' where logonid = 'spiuser';

   2. For Oracle:

      update userreg set logonpassword=x'encrypted_hexadecimal_output' where logonid = 'spiuser';

   3. For Postgres:

      update userreg set logonpassword=x'encrypted_hexadecimal_output' where logonid = 'spiuser';

8. Exit the Docker container.
9. Share the plain text spiuser password with your development team, as they will need it to load the Commerce+ database schema.

What to Do Next