IdStory Identity Manager

We can simulate this behavior with these steps:

• Whole test start from user detail,
• next step is get to identity roles,
• start new request,
• add new role by button,
• find your role by role catalogue select,
• after you find the role click on bussines card, in developer console you can now see new error from role/{ID}/permissions endpoint with 403 code,
• then select this role and add it,
• next error with same endpoint role/{ID}/permissions was thrown and showloading doesn't dismiss.
  

Complete requests:

All permissions settings (userRole) can be found in screen permissions.png

As a workaround, we recommend allowing all users to read all roles they can requested for. This should temporarily solve the problem. The only drawback is that users will see the role agenda, where they will see all the roles they can requested for (read-only). Try this already to verify that the scenario described above applies to customers.

I fixed UX problem with showing multiple showloadings.

Commit : https://github.com/bcvsolutions/CzechIdMng/commit/baf644b5b59cc226e0e1c6250f60f959a6c912a0

I was able to found and fix issue with dequeue request for fetching permission on failed attempt from redux queue (added in #1247).
Thx @svandav and @kopro for help, it was really hard to reproduce.

Commit:
https://github.com/bcvsolutions/CzechIdMng/commit/c1dd1ca5cdc262a479882342509e14d567c24e50

Could you do a feedback, please?

I made feedback on project tomorrow. I will deploy your changes on project (snapshot frontend psst) and test it there.

Thanks for fix and help with debug. I tested same scenarios as yesterday and its work! Thank YOU!