After upgrading Data Aggregator from release 20.2.4 to 21.2.8, and then again from 21.2.8 to 21.2.9 noticed that after upgrade completed in the file /opt/IMDataAggregator/apache-karaf-*/etc/jetty.xml the KeyStorePassword and TrustStorePassword are set to the same value, though these were previously configured to different passwords.
This happens only if customer configured HTTPS on Data Aggregator manually, or manually updated TrustStorePassword after sslConfig.sh tool was run.
The upgrade process assume the two passwords are always the same, so it reads the keystorePassword and then copies jetty-https.xml to jetty.xml and replaces the two passwords with the keystorePass value.
Release : 21.2.x
Component : PM Data Aggregator
Currently this is the expected behavior.
The sslConfig.sh tool by default sets both KeyStorePassword and TrustStorePassword to the same value.
This problem could be seen only when configuring HTTPS on Data Aggregator manually, or manually update/change TrustStorePassword , to set different passwords after sslConfig.sh tool was run.
Workaround is to manually set the passwords to the desidered values in the file /opt/IMDataAggregator/apache-karaf-*/etc/jetty.xml
Defect DE532769 has been submitted to add support for different passwords on Data Aggregator for KeyStorePassword and TrustStorePassword