Reviewing passwords that cannot be migrated

This troubleshooting topic is about passwords that cannot be migrated from FootPrints version 11.0 to FootPrints version 12.0.

Description

• FootPrints version 11.0 and FootPrints version 12.0 use different algorithms when storing passwords. 
• To resolve this incompatibility, when a user logs onto the FootPrints version 11.0 instance, FootPrints version 11.0 calculates and stores FootPrints version 12.0 compatible password information. This data is not used by FootPrints version 11.0, but stored is later used to migrate passwords to FootPrints version 12.0.
• The passwords of users who never logged on after upgrading to FootPrints version 11.0, cannot be migrated to FootPrints version 12.0, because they do not have the prerequisite stored password data.

Resolution

• Before migrating to FootPrints version 12.0, ensure that your FootPrints version 11.0 does not have users with passwords that cannot be migrated.

  Note

  If you fail to ensure that your FootPrints version 11.0 does not have users with passwords that cannot be migrated, you may have the user accounts with compromised or unusable passwords in FootPrints version 12.0.

• The Migration Advisor report includes a list of users that do not have FootPrints version 12.0 compatible password data stored on your FootPrints version 11.0 instance.
  Select one of the following options to address this issue for each user on the list:

1. If the user account is defunct and the user is no longer using the system, to delete the user's FootPrints version 11.0 account navigate to:

   • Administration > System > User Management > Delete Users from Workspaces

   • Alternatively, Administration > Workspace > Edit Agent or Edit Customer

2. If the user has not logged on recently, but is still a legitimate user who might need to log on in the future, you must perform one of the following actions:
   
   • If you have current contact information for the user, allow the user to log in FootPrints version 11.0 before migration.
     This allows the FootPrints version 12.0 to store the compatible password data and use it later after migration.
   • Reset the user's password, that results in the system storing the necessary FootPrints version 12.0-compatible password data. Inform the user that the password was reset.
   • If you are unable to communicate with the user, leave the password as it is, and it can be handled after migration.
     The user is restored on FootPrints version 12.0 with a randomly generated password. The issue is detected and listed in the Things to Do After Migration list in the Migration Advisor report. You are redirected on how to proceed at that point in your post migration process.
3. Regenerate the Migration Advisor report and verify that this issue is resolved.
   The users with incompatible passwords might have either been deleted or they now have passwords that are migration ready.