Identitiy search based on end date attribute

[sahincelik]

Hi experts,

In our environment, I noticed that searching inactive identities based on endDate field is not possible. When I run the query below, it does not return any value despite the endDate identity attribute is already marked as searchable. What could be the possible reasons? Any idea would be appreciated!

[rohitmisal45 (Rohit Misal)]

Hello @sahincelik
It seems like the issue might be related to how the query is structured or how the endDate field is indexed.
I used the modified date attribute in my query and got accurate results. You can try using your endDate attribute in a similar way—it should work if it’s properly indexed and searchable.

[MVKR7T (Krishna Mummadi)]

Your end date is a string not a date, that is the reason.

[iamnithesh (Nithesh Rao)]

Read this document that will help you understand the issue

How to Format Identity Attribute Date Values to Be Searchable in Search

[sahincelik]

How do you know that? Because I already use a transform for startDate and endDate fields, just like described in the guide.

[sahincelik]

Thanks @rohitmisal45, how should I make an identity attribute indexed?

[Santhakumar (Shantha Kumar)]

@sahincelik Get the identity attribute you want to make searchable and got to Identity Attribute API then mark the searchable as true. This will works for your case.

Refer the below link for more info:
put-identity-attribute | SailPoint Developer Community.

Thanks,
Shantha Kumar

[sahincelik]

This was not the issue for me. Despite the guide says we can use date fields in the “yyyy-MM-dd” format and make it searchable, in reality, it does not work like this. It started working after when I change the dateFormat as “ISO8601”.