Upgrade instructions versions 6.x
6.4.0 to 6.4.1
Run all database scripts
- V5_08_01_00__drop_unique_constraint_on_user_id_for_user_client_keys.sql (Oracle and MSSQL only)
6.2.x to 6.4.1
SAML Service Provider configuration
The Signing credentials and Keystore password must be configured via the admin console when using SAML. Populate these fields via the SAML Service provider section in the Admin console.
Run all database scripts
- V5_08_00_00__rename_public_key_to_user_public_key_for_transaction_signing.sql (Oracle and MSSQL only)
6.1.0 to 6.2.0
Run all database scripts
- V6_02_00_00__add_on_delete_set_null_on_pin_policies.sql
- V6_02_00_01__fk_delete_template_sets.sql
- V6_02_00_02__increase_user_agent_in_events.sql
- V6_02_00_03__add_send_badge_number_to_mobile_platform_versions.sql
Migration V6_02_00_01__fk_delete_template_sets.sql
may fail with some variants of MySQL. You will get an error message that the constraints
client_conf_tmpl_sets_id_fk
and templates_tmpl_set_id_fk
do not exist. If this is the case and you manually migrate the database schema, then execute the
following migration instead:
ALTER TABLE `client_configs`
DROP FOREIGN KEY `client_configs_ibfk_1`;
ALTER TABLE client_configs
ADD CONSTRAINT `client_conf_template_set_fk` FOREIGN KEY (`template_set`) REFERENCES `template_sets` (`id`)
ON DELETE SET NULL;
ALTER TABLE `templates`
DROP FOREIGN KEY `templates_ibfk_1`;
ALTER TABLE `templates`
ADD CONSTRAINT `templates_template_sets_fk` FOREIGN KEY (`template_set`) REFERENCES `template_sets` (`id`)
ON DELETE CASCADE;
Update package names for custom Token Server plugins
The package names for one of the Token Server modules have been changed from com.innovation_district.*
to com.onegini.oauth.*
. You might need to update any
Token Server plugins that import any of the com.innovation_district.*
classes.
6.0.0 to 6.1.0
Run all database scripts
- V6_01_00_00__add_on_delete_cascade_to_various_tables.sql
- V6_01_00_01__multiple_custom_authenticators.sql
- V6_01_00_02__drop_fido_support.sql
Adapt Docker Compose variables
Remove the following variables:
- TOKEN_SERVER_COMMON_FEATURES_FIDO_ENABLED_BOOLEAN
Multiple Custom Authenticators
The Token Server supports multiple Custom Authenticators. In the previous versions the Custom Authenticator was automatically linked to a Mobile Authentication Type or Application. From this version you need to select the Custom Authenticators for an Application or Mobile Authentication Type.
For MySQL the existing Custom Authenticator is automatically linked to the Mobile Authentication Types with type "Push with Custom Authenticator" and to Applications that have checked "Custom Authenticators enabled".