vCenter Single Sign-On failure after changing SQL Server port

Working on one of the systems recently on which SQL Express was installed locally on the same VM as vCenter (hence the default SQL port was dynamic), I had to create a database for another application for a remote system and in order for the communication to happen, I changed the dynamic SQL Server port to the standard 1433.

Guess what? After the change, the single sign-on service would refuse to start. Upon research, I was taken to a VMware KB 2033516. The explanation and some screenshots based on the KB are depicted below.

Step 1. Modify the SSO Setting.

Step 2. Make the port modification in the config file.

Step 3. That's it. Restart SSO and vCenter Service and you are back in business.

Please note that the password values and hostnames are cleared from the config file screenshots.