in short we want to remove the role from the cache of all tenants having the role which was updated.
you change add/remove permission from existing user through application UI should reflect immediately.
Through app UI will work. But you are changing the permission directly in the database.
Can you help us with location in identity service and/or administration service where and how abp is maintaining the permission cache for add , update and remove?
This does not sound right as in real word application once you change add/remove permission from existing user through application UI should reflect immediately. For example i want to delete block the user from using the application with immediate effect or remove/add a role/permission. in this case at least on re-login the changes should take effect.
hi
can I know what should I do in order to make the changes instantly reflected on the UI after updating the permissions manually from the database.
You'd better not do this. Always do it through code.
The framework will use
IDistributedCache<PermissionGrantCacheItem>
to cache the permission grants.AbsoluteExpiration and SlidingExpiration) used when you don't specify the options while saving cache items. Default value uses the SlidingExpiration as 20 minutes.
https://abp.io/docs/latest/framework/fundamentals/caching#abpdistributedcacheoptions
You can clear the
PermissionGrantCacheItem
cache from redis.
Even if we do populate permission through Database ,logout and relogin should repopulate the permissions correctly. isn't it? user does not have to wait for 20 minutes. moreover we have seen that the permissions to take affect take more than 2 hours at times.
Hi all, it seems like ya are not read my comment well, I'll migrate to 51 but if you guys read the migration guid react expo recommend to update version incrementally. I'll migrate today to 51
https://reactnative.dev/docs/upgrading#expo-projects
Thanks, Masum
Just a gentle reminder to get update on this?
Any update on this?
Do we have any tentative timeline as we need to scope this in our sprint planning.
Ok,sorry for the confusion and thanks for the update.
Hi Masum, could you please confirm that you are now migrating to latest expo SDK 51.