Troubleshooting guide

100 A: Migration Data Conversion
RSA Authentication Manager 6.1 to 8.1 Migration Guide
Migration Report
When the migration completes, it generates a migration report that lists which data
was successfully migrated, which data failed to migrate, and any changes that were
made to the data to accommodate the new logical model used in
RSA Authentication Manager 8.1.
• Parameters and options you selected for the migration.
• A summary of the dump file analysis results, including which type of data was
found in the dump file.
• A list of the objects migrated, including users, user groups, tokens, agents,
policies, administrative roles, and extension data.
• Any issues related to the format of your data that you need to resolve to ensure
that your migrated Authentication Manager functions correctly and securely.
Use the version 6.1 Database Administration application to fix any of the
formatting issues that you find in the migration report.
The following sections outline some of the issues that you might see in the migration
report and describe how you might clean up your data in version 6.1, so that you can
restore the version 8.1 database and then migrate again:
• M
igrating User Extension Data on page 100
• Users in Multiple Groups in Different Sites
on page 102
• Activations on Restricted Agents When LDAP Synchronization Jobs Do Not
Contain Group Data on page 103
• PIN Options for Emergency Codes
on page 103
• Add SecurID_Native as a Method of Administrator Authentication
on page 104
Migrating User Extension Data
In RSA Authentication Manager 6.1, extension data can be defined for individual
objects only (such as individual users, groups, agents and tokens), and cannot be
defined on a system-wide basis (so you cannot define one set of extension data for all
users, all groups, all agents, or all tokens).
In version 8.1, user extension data is similar to the 8.1 concept of user attributes. Like
user extension data, users attribute can be used by administrators for querying and
reporting purposes. However, in version 8.1, these settings are system-wide. These
settings can also be used to delegate administrative tasks and allow an administrator to
manage users with a specific attribute. For example, a role might allow an
administrator to manage all users with a certain job title, where “job title” is a user
attribute. A role might also allow an administrator to manage all users in a specific
department, where “department” is a user attribute.