• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 117 views
  • Users 0 members are here
Options
Related

[One Identity Manager 9.3] Best way to store and sync extra attributes from source system not available in UNSAccountB

erick goncalves
22 hours ago

Hello everyone,
I'm working on an integration with an external database in One Identity Manager 9.3, where I'm synchronizing accounts into the UNSAccountB table. However, the source system contains several attributes that do not exist in the standard UNSAccountB structure, such as email, employeeType, and others.
I'm unsure about the best approach to handle these additional attributes without breaking alignment with the 1IM data model and while maintaining object integrity. I also need to be able to synchronize these additional attributes into the Person table after syncing to UNSAccountB (or whatever the best solution may be).

Parents
  • 0 11 hours ago

    Hi,

    It is perfectly acceptable, and standard practice, to extend the schema to accommodate additional attributes.  The schema extension tool is provided for this purpose.

    You could use templates on the Person table to populate the attributes from UNSAccountB but this would usually require the UID_UNSAccountB to be an attribute on Person (to achieve the FK relation and 'trigger' the templates).

    Alternatively, you could use a variation of the ADS_ADSAccount_Update_UpdatePerson process functionality - you'd need to create your own custom version.

    HTH, B.

  • 0 5 hours ago in reply to Barry Jackson

    Thank you very much for the clarification! I just have one more question: for SaaS environments, I found this note in the documentation:

    "To ensure our One Identity operations team can manage, monitor, and perform upgrades to the One Identity Manager cloud components, all customizations to the offering are strictly prohibited."

    In this case, does it mean that extending the schema or performing any similar level of customization is not recommended in SaaS environments?

Reply
  • 0 5 hours ago in reply to Barry Jackson

    Thank you very much for the clarification! I just have one more question: for SaaS environments, I found this note in the documentation:

    "To ensure our One Identity operations team can manage, monitor, and perform upgrades to the One Identity Manager cloud components, all customizations to the offering are strictly prohibited."

    In this case, does it mean that extending the schema or performing any similar level of customization is not recommended in SaaS environments?

Children
No Data