Update attribute metadata for new authoritative source?

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.3p3

Share all details about your problem, including any error messages you may have received.

I’m in the process of migrating a select group of identities to use a different authoritative source app. I’m noticing as I’m testing this in our lower environments, that the identity loses the attribute values that are sourced from the old authoritative app and doesn’t get them back until a new aggregation of the new identity source (even though both sources are correlated to the identity). Is there a way to run an id refresh that also refreshes the attribute source mappings/metadata logic? I know I can solve this setting the new source at a higher priority in the identity mappings for that attribute, but I’d rather not fool around with my identity mappings for the entire environment if at all possible.

TIA!

2

did you try refresh identity cube with refresh identity attribute option checkd?

3

@josefismael

  1. Identify the Source Attributes:
  • Understand what attributes (firstName, lastName, email, department, manager, etc.) are coming from the new authoritative source.
  1. Open the Identity Attribute Metadata:
  • In SailPoint IIQ, go to Setup → Identity Mappings or open the Identity Configuration (identityMappings.xml).
  • Alternatively, open it from the Debug → IdentityAttribute objects.
  1. Update or Add New Attribute Mappings:
  • If new attributes are coming (example: costCenter, employeeType), you need to define them.
  • Set:
    • Display Name
    • Internal Name
    • Type (String, Boolean, Integer, etc.)
    • Whether it is required, multivalued, or searchable
    • Description (optional but good practice)
  1. Modify the Identity Mappings (if needed):
  • Map the new source attributes to existing Identity fields, or create new fields if necessary.
  • Example: Map workdayTitle to title attribute in Identity.
  1. Save and Test:
  • After updating, aggregate accounts from the new source.
  • Check if the identity attributes are correctly populated.
  1. Refresh Identity Cube:
  • Run a Refresh Identity Attributes task to ensure all identity cubes reflect the new metadata.
4

Thanks - the issue here is that I want to change the AttributeSource application from one app to another. It seems the only way I can accomplish this is by putting the new attributesource entry at a higher priority than the old, but I can’t do that for all identities.

1 Like