Configure Username Recovery Configuration On Demand Migration at Initial Start Up

[Malith-19]

Describe the issue:
Username recovery was controlled through the Username.Recovery.Notification.Enable configuration so far. With the introduction of the new sms channel support feature for the username recovery flow, two new governance connector configs have introduced Recovery.Notification.Username.Email.Enable and Recovery.Notification.Username.SMS.Enable which will enable the email and sms channel for the username recovery flow.

During the initial read of the resident IDP, the Username.Recovery.Notification.Enable config is enabled(this will enable the username recovery) and the Recovery.Notification.Username.Email.Enable config will be enabled default to keep the existing behaviour for the user. Recovery.Notification.Username.SMS.Enable config will be disabled by default.

However, with the new SMS channel, one can decide to enable SMS channel for all username recovery config(Recovery.Notification.Username.SMS.Enable) through the on-demand migration by enabling toml config ConfigSwitching.OnInitialUse.EnableSMSUsernameRecoveryIfConnectorEnabled.

On Demand migration behaviour:

• Migration will automatically run during the first read operation of the resident IdP for each tenant.
• The existing users who have username recovery enabled, will have the email option enabled and sms option disabled by default.
• A new toml config was introduced to change this behaviour to enable SMS option through on demand as well
• Config : ConfigSwitching.OnInitialUse.EnableSMSUsernameRecoveryIfConnectorEnabled deployment config.

Related issues

• SMS support for username recovery flow #21180