Versions Compared

Old Version 1

changes.mady.by.user Unknown User (s.wartenberg)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (s.wartenberg)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Changes in default password properties

With the upgrade to Spring Framework 5.0 the password storage has undergone a major change to provide more secure defaults. This means that passwords are now stored in an encrypted way by default. Existing passwords in publisher.properties should all be prefixed with {noop} to ensure that any existing plain text passwords will still work. The encryption algorithm is Bcrypt.

Please update the oauth2.secret accordingly.

Example

In Publisher 4.0.x the oauth2.secret would look like this:

Code Block
languagebash
oauth2.secret=123

In Publisher 4.1 you have two choices, either set the password without encryption:

Code Block
languagebash
oauth2.secret={noop}123

Or with BCrypt encryption:

Code Block
languagebash
oauth2.secret={bcrypt}$2a$04$zMrh.OEz/qDyPZnP14vMwucVpS5rTI91NZDHhW6fVG2sA.9NPGG16


You can encrypt your passwords using an online BCrypt tool such as: https://www.devglan.com/online-tools/bcrypt-hash-generator

Panel

On this page:

Table of Contents
maxLevel1

Publisher database upgrade

As the Publisher 4.0 aligned with Blueriq 10, the database columns are updated from VARCHAR to NVARCHAR. Therefore Blueriq has updated it's schema. Also, due to the upgrade to Hibernate 5 (which is more strict then older versions), Blueriq leverages on the default Hibernate behavior for generating ID's. This means Blueriq does not rely on IDENTITY columns anymore and introduced SEQUENCES to be more in sync with Oracle. 

The scripts can be found in the Publisher installation zip in dbscripts/publisher and dbscripts/publisher-client.

Panel

On this page:

Table of Contents
maxLevel1

Upgrade steps

Note
The steps should be executed by an experienced DBA-er and all necessary precautions should be taken before migration.

Step 0: Backup the database for publisher as well as publisher-client.

Step 1: Run either mssql_update_4.0.0_script_01.sql or oracle_update_4.0.0_script_01.sql. This will rename the current tables.

Step 2: Run either oracle.sql or mssql.sql. This will create the new tables.

Step 3: Run either mssql_update_4.0.0_script_02.sql or oracle_update_4.0.0_script_02.sql. This will copy the data from the old tables to the new tables.

Step 4: Test the publisher and publisher-client so you know everything works as expected.

Step 5: Run either mssql_update_4.0.0_script_03.sql or oracle_update_4.0.0_script_03.sql. This will remove the old tables.

Changes in third-party libraries

Please take a look at the Blueriq Publisher 4 libraries