Please share any images or screenshots, if relevant.
NA
Please share any other relevant files that may be required (for example, logs).
NA
Share all details about your problem, including any error messages you may have received.
We have an application where approximately 10,000 locations are defined, and each location has 18 permissions that need to be configured in SailPoint. This would result in around 180,000 entitlements being created in SailPoint.
There are additional applications that follow a similar pattern, which may significantly increase the total number of entitlements.
We are evaluating SailPoint’s performance and scalability for handling such a large volume of entitlement data.
We have the following questions:
Is SailPoint capable of handling such large volumes of entitlements (e.g., 180,000+ entries)?
What are the best practices to manage such a scale efficiently in SailPoint?
First need to understand are theses 18 permissions same across 10k locations, if yes then location can be defined in a custom object and pass this only during the api call, same way during aggregation traverse through this custom object and aggregate using rules. You cannot really define those many entitlements. You need to check with application team are these granular level permissions if yes can they do modelling in such a way, group some of the granular permissions to a entitlements or a group defined at target application end.
As you are saying multiple applications follow this pattern you cannot define those many 18k entitlements which will create performance issues in longer run - with UAR’s, identity refresh calculations.
Hi @skingare, we have applications with more than 300,000 entitlements.
We haven’t had performance issues resulting from that, but it may vary depending on what you are doing with them.