Troubleshooting guide

A: Migration Data Conversion 101
RSA Authentication Manager 6.1 to 8.1 Migration Guide
In version 8.1, there are default user attributes (such as User ID and Password),
internal attributes, and custom attributes. A custom user attribute is known as an
identity attribute definition. Identity attribute definitions can be mapped to the internal
database or an external identity source to retrieve attribute values from users. For
example, suppose that you add a “Location” attribute that represents the office
location. If you have locations in London, New York, and Madrid, you can add each of
these locations as predefined values that are stored with the user record in the identity
source. You can also select the type of data that you want to store in the new attribute
such as string, integer, or Boolean data, and what values are associated with the
attribute. For more information about user attributes and identity attribute definitions,
see the RSA Authentication Manager 8.1 Administrator's Guide.
Because you cannot define extension data on a system-wide basis in version 6.1, it is
possible that the 6.1 database contains multiple extension fields with the same data
that is inconsistently named or is given an inconsistent format. To avoid migrating
duplicate extension data that is only formatted differently (for example, by letter case
or punctuation), you can select an option to consolidate this data into an attribute. If
you do not merge duplicate extension data, migrated users may be defined with
multiple attributes that are the same.
Depending on whether you perform a test migration or add identity attributes prior to
migration, the user extension data in version 6.1 may be migrated differently. In all
cases, the user extension data is migrated as a custom identity attribute definition. The
following table explains how the 6.1 extension data is migrated based on the state of
8.1 and the state of the data you are migrating.
State of Version 8.1 Migration Result
A migration occurs for the first time and user
extension data is migrated into version 8.1
with no conflicting user attributes.
The data is migrated.
A 6.1 dump file contains conflicting
extension data that shares the same name,
but contains different values.
If you do not select to merge 6.1 extension
data, only one attribute and the associated
value is migrated. The other user attribute is
skipped during the migration.
If you choose to merge extension data, the
data is migrated as an attribute with multiple
values.
You manually created a user attribute that
matches version 6.1 user extension data
before the attribute is migrated.
After migration, the duplicate user attribute is
migrated with the "AM61_" prefix.
A single valued attribute that was previously
migrated on version 8.1 is migrated again
but now includes new attribute values. The
data type has not changed.
The attribute value is updated.