Creating a Custom identity attributes using IdentityExtended.hbm.xml file

Identityiq V8.0

I trying to create a custom identity attributes after a clean installation. I have updated Database with proper mapping and also in the identity mapping in UI. Please help me what am I missing.

  1. Updated IdentityExtended.hbm.xml for custom identity attributes
  2. Updated the Database with proper mapping
  3. Mapping made in UI in identity mapping by creating a new identity attribute.
  4. I didn’t removed extended1 extended2 columns from DB. And I’m not sure about extended_identity1 columns

Hi @pradeepkum,

all the step are correct, have you restarted the tomcat?

Also, How you have configured the attribute into the IdentityExtended.hbm.xml, db and ui? can you share same screenshot?

Those colums are for extend attribute with identity like type(for example manager)


I’m getting the same error even after tomcat server restart. Sailpoint is going down when after tomcat restart.

I have created an New Identity Attribute in Identiy mapping added the same value as a name: custEmployeeId.

ok, it looks good.
On the Identity Object Config, did you have add namedColumn="true" on the searchable attributes?

It was not added before. But even after adding it still the same.

you must remove the extendedNumber.

A searchable attribute could managed with ext.number and it will stored on a columun extendedX or you can managed with namedColumn and it will stored in a column with the name of the attribute.

Removed the extendedX and restarted the tomcat server. Its still the same exception error

One thing you did not specify is how you generated the commands to update the database. Did you use the .\iiq extendedSchema command or did you sort of make up the file based on some other process?

I generated using ./iiq extendedSchema and only performed update in identity table in database.

Ok, so into the logs you somenthing else?

Sailpointlog-Jan-25-2025.log (798.4 KB)
Sailpointsafelog-Jan-25-2025.log (4.0 MB)

I only see the error related to SessionFactoryRegistry with for class object.Identity

safelog file is when its working fine.

Its working now.

Solution: We should add (access=“sailpoint.persistence.ExtendedPropertyAccessor”) all the custom identity attributes that are defining.

Thanks to @enistri_devo

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.