Has anyone been brave enough to make the jump?!
Ah ... WHOOPS! I jumped in and then had to roll back ...
The release notes didn't say anything about needing to reconfigure the setup and hardening the passwords for the PostgreSQL database credentials upon first launch after the upgrade. This was a surprise, and I didn't have those details at hand when running the upgrade installer. Haven't needed those for quite a few upgrades.
In fact the "Before you upgrade!" section in the Release Notes has no content. ?!?!?
Luckily I took a snapshot of the server and was able to roll back to it successfully.
Gonna need to research how to proceed before running this again.
Thanks for highlighting , the steps are mentioned in the release notes under - Secure Communication to database . We will add it to "Before you upgrade"
Ah ... I see. Thank you for the quick reply, Avadhut.
I didn't take a lot of notice of the New Features and Improvements section of the Release Notes, assuming them to be generally informational about changes in the application. Didn't realise the subsection on Secure Communication was important instructional advisory info and needed to be understood and catered for in completing the upgrade.
I missed this first time round as well, would have been nice for Installer to check for this automatically as I'm sure there will be more who fall down on this creating unnecessary support cases.
Do the secure communication to database improvements include being able to use Windows authentication for SQL Server authentication?
Stop It! I almost dropped my coffee mug seeing that!
Concerning this part specifically: "...upgrades the cryptographic algorithms between WHD and a database."What were the updates to those algorithms? Due to our legacy database cluster, I still have to re-enable TLS 1.0/1.1 within '..\WebHelpDesk\bin\jre\conf\security\java.security' to even be able to connect to our database. Basically...jdk.tls.disabledAlgorithms=SSLv3, <span style="text-decoration:line-through;">TLSv1, TLSv1.1</span>, RC4, DES, MD5withRSA, \ DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \ include jdk.disabled.namedCurvesWill upgrading stop me from being able to do this?
jdk.tls.disabledAlgorithms=SSLv3, <span style="text-decoration:line-through;">TLSv1, TLSv1.1</span>, RC4, DES, MD5withRSA, \
DH keySize < 1024, EC keySize < 224, 3DES_EDE_CBC, anon, NULL, \
include jdk.disabled.namedCurves
I would check with support on that one.
Ticket submitted.