Can SailPoint Support Increase the Additional Searchable Identity Attributes Limit Beyond 6?

Hello,

We have reached the limit of 6 additional searchable identity attributes in our SailPoint tenant.

I tested the API and was unable to add more searchable attributes beyond this limit.

We need additional searchable attributes to support our Account correlation definition, and the current limit is becoming a constraint.

Has anyone successfully worked with SailPoint Support to increase this limit for their tenant ?

I have already submitted a support ticket, but I’m waiting for their feedback.

Thanks in advance for any feedback or experience you can share.

@baoussounda,

I haven’t looked at this in years, like 8 years since we went live, but this was a hard limit last I knew. That said, there are quite a few things now where, if you reach out to your CSM and open a ticket, they can increase beyond the default assigned to each tenant (tagged entitlements being one example).

That said, looking at a recent article (updated May 16th of this year), it does still appear to cap correlation attributes at 6:

API to Extend Customizable Correlation Attributes - Compass

Thanks!

Thanks @Justin

Right, when using the API, the response clearly indicates that the limit for searchable identity attributes has been exceeded.

In the past, SailPoint has increased some tenant limits for us (changing them from soft limits to hard limits), such as the maximum number of Access Profiles per app, number of roles or access profiles.

I’ve already submitted a support ticket and am waiting for SailPoint’s feedback.

Thanks!

I don’t think, there is no tenant-level setting or API that allows customers to increase this limit themselves.

Thanks,

Mahesh

It may be worth an ticket to see if there are any options available or if they intend on extending this in the future.

You did a right thing!

Please keep us posted on SailPoint Support’s response. If this is possible, I would also like to increase the number of additional searchable attributes in my customer’s environment.

I don’t think there is a flexibility for this

Hi @baoussounda,

We encountered a similar issue and reached out to SailPoint for recommendations. Unfortunately, there was no workaround available that met our requirements.

They did share the following discussion thread, which may be helpful:

Additionally, please consider voting for this enhancement request on the Ideas Portal: https://ideas.sailpoint.com/ideas/GOV-I-5077

Hopefully, this helps. Let us know if you discover any alternative approaches.

We had a similar situation and our work around was to use Account attribute from the auth source for correlation instead of identity attribute.

Using String matchedName = idnRuleUtil.attrSearchGetIdentityName(........) we get the identity name reference and then update the return map as below:

if (matchedIdName != null) {
returnMap.put("identityAttributeName", "name");
returnMap.put("identityAttributeValue", matchedIdName);
return returnMap;
}

For this you need to promote account attribute as searchable and there is no limit on that