Hi,
When aggregating the entitlements, they are loaded properly, but those entitlements are not displaying in the entitlement catalog, and if we change those as requesable from the source, they are not displaying in the request center. can anyone help me resolve this?
Hi @kani1,
Can you share your account schema configuration and entitlement type configuration here to check further.
Thank You.
Bapu.
entitlement shema
account schema
c
yes its enabled for entitlements
In image 1 remove entitlement tag to id keep empty and same image 2 as well in roles type. perform entitlement aggregation and check.
1 Like
tried this , but no use .still the entitlements are not displaying in the catalog
Could you let me know which connector are your using currently. can you share screenshot of your entitlement tab in source as well.
1 Like
is this an issue ?
We have the exact same issue in Production
1 Like
how did u resolve it ? can u help ?
We have not resolved it yet. We have opened a support case to get SailPoint Assistance to figure out what happened to our entitlements.
On an aside we have notices a new feature on sources: “Try new experience” on our test-tenant.
When using this new feature Our Entitlements are visible through this experience…BUT they are still missing from Searches and “Admin” - “Access Model” - “Entitlements”
2 Likes
Entitlements missing are from a WebServices “Rest-Api” source. And we are able to see the source-aggregation recognizes th eAccounts and Entitlements…we’re just not able to work with anything.
We have same issue.
Sailpoint updated Web Service connector with “New Experience”. I guess that the messed up the connector. Currently we cannot work in production.
Support case was opened 4 hours ago.
Right now we are having a hard time just trying to someone to look at the case at Sailpoint support. 
2 Likes
Let’s hope they’re so busy fixing stuff that they have no time responding to tickets
1 Like
Our issue got resolved after 5hours. The entitlements are showing up in “Access Model” - “Entitlements” after 5 hours. and it is taking time to change its requestable status too.
Yes we have the same result today. Our Entitlements are back…but none are requestable.
We have a script that runs every 30 minutes to check for new nonrequestable Entitlements from a specific Source, to make them requestable.
This does not seem to have any effect on any of the Entitlements yet.
There is a feature suggestion in the iedas portal that would have mitigated the immediate problem: https://ideas.sailpoint.com/ideas/GOV-I-3741
I would suggest everyone votes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.