After an upgrade from Sense 3.1.4 synchronized persistence to 3.2.0 shared persistence fails, it could be stated in the xxxxxx_QLIK_System_Repository_log
"Fatal exception password authentication failed for user "qliksenserepository" and that could be caused by the repository database user password (which is for the qliksenserepository user) is different, so it can´t connect to the qliksenserepository.
Log error:
ERROR Qlik System.Repository.Repository.QRSMain 9 3a3cb40d-dd2b-4aa2-8c5b-2b3687951481 DOMAIN\user Fatal exception password authentication failed for user "qliksenserepository"↵↓The provider did not return a ProviderManifestToken string.↵↓An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure.↵↓An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it
The workaround is to look up the password in the ConnectionStringEditor and paste in to the pgAdmin repository.
Run the ConnectionStringEditor application "
C:\Program Files\Qlik\Sense\Repository\Util\ConnectionStringEditor".
Look up the Password='xxxxxxxx'.

Next step is to open and connect to the pgAdmin3 repository "
C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.3\bin" and add the password into the repository.
Under the servers/Login Roles/qlksenserepository properties can you add the password from the ConnectionStringEditor.