Can anyone please explain what is the difference between “extended1” and “extendedIdentity1”?
in IdentityExtended.hbm file there are 5 “extendedIdentity” attributes are present which are separate columns in database, want to understand where and how it can be utilized.
In SailPoint IIQ, you can create extended Attributes of two types. One is string, and the other type is Identity object.
By Default extended attributes of type string is present in the format of “extended1“ and extended attribute of type Identity is present as “extendedIdentity1“
extendedIdentity1 is used when you want to store the identity details in the identity attribute in order to link one user with a different user. For Example - Manager field contains a link to the Identity and it stores the Idenitty object of the manager.
In SailPoint, we can create attributes of type String or Identity.
extended1 attributes are of type String and are used to store details about an identity (ABC), such as name, address, and other related information.
And, extendedIdentity1 attributes are of type Identity and store references to another identity. For example, the manager (XYZ) of identity (ABC), where the manager is also an identity in SailPoint.
Both extendedIdentity1 and extended1 are defined in the HBM files and are represented in the SailPoint UI as attributes of type Identity and String, respectively.
@Prash I hope details shared by fellow Sailors helped you out. If yes, could you please accept the valid response as solution, so it can help others having the similar issue.
@Prash I’m really impressed that you’re trying to understand the system design at a deeper level. That’s really great. I’m assuming you’re referring to this point from the IdentityExtended.hbm.xml file.
<property name="extended1" type="string" length="450"
index="spt_identity_extended1_ci"/>
<many-to-one embed-xml="false" name="extendedIdentity1" class="sailpoint.object.Identity"/>
extended1 is for custom text data, while extendedIdentity1 is for identity-to-identity relationships such as mentor, backup approver, or secondary manager.
below content from sailpoint configuration files.
By default we will map 10 extended attributes, but this may be raised to
a maximum of 20. Using ExtendedPropertyAccessor can add attributes beyond
the limit of 20 and have meaningful names. Example of ExtendedPropertyAccessor
is shown below.
Only the first five attributes are indexed, to provide
an example of how to specify an index. In a production deployment you
will usually index most of the extended attributes since they are
usually added for searching, but index maintenance slows down updates to
the identity cube so add them only if necessary.