Last Modified: Sep 06, 2019
See more info
BIG-IP APM, Install/Upgrade
Known Affected Versions:
13.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 13.1.1, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.3, 14.0.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.0.1, 14.1.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.2
Opened: Feb 12, 2019
The database from a prior configuration does not seem to have any tokens. The tokens are being stored in a new database with a different name.
Old database seems to have lost tokens. In the case of these two database instances: oauthdb oauthdbprod Because the name 'oauthdb' is also present in the name 'oathdbprod', the system creates a new database instance of 'oauthdb' at upgrade, so oauthdb will have an empty database.
Upgrade from v13.x. -- The name of one OAuth database instance is duplicated entirely in another instance name (for example, 'oauthdb' and 'oauthdbprod').
Before upgrading, do the following: 1) Copy database oauth to another database with a completely different name. 2) Copy tokens in new database to the old, empty database.
The new database instance is no longer created created, so the old database now retains tokens after upgrade.