Upgrading components
This section contains notes about possible issues that may occur with the component framework when upgrading.
Upgrade from 11.1.3 to 12.0.x fails with component error’Failed: AUTO_INSTALL for Scenario.hid_authchain_smspin_email
In Bravura Security Fabric 11.1.3 the Scenario.hid_first_login and Functional.hid_authchain_2factor components were changed from using the generic Scenario.hid_authchain_smspin to Scenario.hid_authchain_smspin_celltrust even though the replacement for Scenario.hid_authchain_smspin was logically Scenario.hid_authchain_smspin_email.
In 12.0.1 this changed back from celltrust to email, but those who installed 11.1.3 with this scenario will run into a conflict until Bravura Security Fabric includes the ability to specify multiple possible dependent components.
Work-around: To fix this, explicitly remove Scenario.hid_authchain_smspin_celltrust and reload the components, the conflict should resolve itself.
Upgrade cannot compensate for custom components
An upgrade using the setup installer will not be able to compensate for custom components. For example if the manifest of a custom component depends on a component that has been deprecated, upgrade will not be able to properly load that custom component because of the deprecated dependency. If the custom component has a CSV that does not use newer columns this could cause a failure during upgrade.
Check custom components before upgrading.
Entries in the external data store may not be upgraded properly
As of version 11.1.1, Bravura Security Fabric no longer supports the use of wildcards in external data store entries. After upgrading to 12.3.0, any entries in the external data store that uses wildcards may not be updated properly. Those entries will need to be manually fixed.
Update system vault addresses
After upgrading from a version 10.1.4 instance you must manually update the address of system vault types that were created before the upgrade as their address lines will still contain single quotes. If the address line is not updated the creation of vault accounts will not have set passwords.
Upgrade cannot install all decoupled components
When a component is decoupled to multiple components, only one component will be installed during upgrade; others will need to be manually installed after upgrade.
For example: Component Scenario.im_corp_onboard was decoupled to components Scenario.im_corp_onboard and Scenario.im_corp_automated_onboard since 11.1.1. If component Scenario.im_corp_onboard was installed on a 10.0.4 instance, when upgrading to 11.1.3, the upgrade task will only upgrade the Scenario.im_corp_onboard component. Scenario.im_corp_automated_onboard won’t be installed during upgrade.
The workaround is to manually install the component Scenario.im_corp_automated_onboard after upgrading.