Upgrade script normally does only core ... not addons.
Suggest cloning your site to a test instance first which has your mfa plugin and testing upgrade there first.
Do you have this one:
shows compat up to 4.2.
If so, might contact the providers/maintainers of that plugin and inquire about 4.3. It is maintained by Catalyst IT and they have been involved with Moodle for a very long time.
The 4.3 index.php file for that tool does show:
* MFA configuration page.
*
* @package tool_mfa
* @author Mikhail Golenkov < golenkovm @ gmail . com >
* @copyright Catalyst IT
*
* @package tool_mfa
* @author Mikhail Golenkov < golenkovm @ gmail . com >
* @copyright Catalyst IT
'SoS', Ken
Did you get through? If not, just don't move the old MFA plugin folder to the new moodle code. It's already integrated into it. You'll have to remove the sms, loginbanner, and another one (can't remember, secq) after the upgrade.
Hi Zoran, how did the moodle upgrade go, did users have a smooth transition from the MFA plugin to core or did they have to start from scratch again ?
Hi Paul
Even though you asked Zoran, I post a short answer ;) We did the upgrade from Moodle 4.1 (third party MFA-plugin) to Moodle 4.3 (Moodle MFA in core) - our users did not have to start from scratch. If you are planning on upgrading from the third party plugin to the core plugin, you might check https://github.com/catalyst/moodle-tool_mfa/issues/457 (a manual downgrade of the plugin version of mfa_factor_token in the Moodle DB was necessary in our case).
Best,
Samuel
We had only few users with MFA enabled so we uninstalled MFA plugin, upgraded Moodle and enabled new MFA feature. Users set up their MFA factors again but it was no big deal because there were only few of them at the time.