Bug: Classic to New Experience Realm Migration Does Not Show All Classic Realms

Version Affected: 22.02 HF2 through HF8 inclusive; 22.12 Base through HF2 inclusive
Bug Number: EE-3175
Bug Status: Closed — Fixed
Fixed in Version(s): 22.12 HF3

 

Overview

After enabling Classic to New Experience Realm Migration by following the Classic Experience Migration to the New Experience guide, some Classic Realms may not appear in the list of Realms available for migration.

 

Cause

There are two known causes for a Realm not appearing in the Classic to New Experience Realm Migration list:

• The Realm uses one of several PostAuth types not currently supported for migration from Classic to New Experience. See the list of unsupported Realm PostAuth types.
• If the missing Realm is not one of the unsupported PostAuth types above, the Migration Tool may be unable to read the Realm correctly because of the Realm's folder name. The log file in D:\SecureAuth\AdminApiLogs shows an error similar to the following:

Error|SecureAuth.Admin.API.Controllers.API.V3.MigrationController|Error trying to get migration info for realm 'secureauth5'|System.FormatException: Input string was not in a correct format.
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at System.Convert.ToInt32(String value)
   at SecureAuth.Admin.API.Controllers.API.V3.MigrationController.<>c__DisplayClass7_0`1.<GetAndIterateClassicRealms>b__1(String migratableRealm)

Resolution / Workaround

If you're on a version before the fixed version above, the folder-naming cause described above can be worked around as follows:

1. Rename the Realm folder to ensure it starts with an uppercase S. For example, change secureauth5 to SecureAuth5.
2. Exit the Classic Migration page and open it again. The Realm should now be present for migration to the New Experience.

If the missing Realm instead uses an unsupported PostAuth type, there is no workaround — that Realm type is not currently eligible for migration.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.