Activities of "aziz.bouhejba"

It's gonna take me a long time to do that (create a new microservice solution with Blazor Web App UI / integrate cms kit in some service, expose it through gateway etc..) We didn't find any documentation working on it, can you give me a working sample of CMS kit with our actual setup instead? We'll fix it from there? it's reassuring at least to know it's supposed to be working properly.

Hello,

We're integrating CmsKitPro into a Blazor Web App, and currently have the following setup:

• CmsKitProAdminBlazorWebAssemblyModule added to the WebApp.Client (WASM) project
• CmsKitProAdminWebModule added to the WebApp (Server) project

The issue we're experiencing is that the UI between the two modules appears inconsistent. And:

When we navigate to a CmsKit page (e.g., from the blogs menu) and reload the browser, the app falls back to the server-side view, which looks bugged or non-functional.

If we navigate elsewhere in the app and then return to the CMS section, it starts working again as expected — showing the correct WASM view.

Do you have any idea what might be causing this behavior? Is there a best practice for integrating CmsKitPro in a Blazor WebApp app to avoid this?

Other infos, we have the back-end part setup in a microservice and it works well on the wasm to create/edit blogs and posts.

Thanks for your help!

results on our end:

• Blazor web app : works fine
• MAUI Blazor hybrid app : works fine locally / when deployed on the android-apple stores, doesn't work.

We are gonna try a custom solution to clear redis cache of user because we have no time dealing with this..

Our Redis cache solution works

yes I did

Hi!

tried the new proposed solution, doesn't work on our Blazor Web app. both proposed solutions also don't work for our MAUI Blazor hybrid mobile app.

We need the dynamic claims to also work on mobile app.

Thank you

yes it works.. thank you. I guess it's a template issue then?

yes done that, same issue

Reproduction Steps:

1. Create a new microservice solution.
2. Create a new tenant.
3. Log in as the tenant admin.
4. Create a new role called "Guest".
5. Create a user named "TestUser" and assign the "Admin" role.
6. Open an incognito browser and log in as TestUser.
7. Confirm that TestUser has admin privileges — ✅ expected.
8. Log out TestUser.
9. As admin, modify TestUser’s role to "Guest" (remove admin role).
10. Log in again as TestUser (in incognito).
11. TestUser still has admin privileges — ❌ unexpected.

Expected Behavior:

After logging out and back in, TestUser should have Guest permissions only, with admin privileges revoked. According to the ABP documentation, role changes should take effect at the next request or at least after reauthentication. For us it doesn't even work with a logout/login

Actual Behavior:

Role changes are not applied even after logout/login. It seems role claims are cached or not refreshed properly.

Only solution we found right now is creating a redis cache service and deleting user cache (not ideal)..

Hello, we noticed that when demote/change the role of someone, it doesn't get reflected instantly. we figured it's because caching. but we thought UseDynamicClaims covered that case.

We don't want an admin that we demote to a simple guest to still have admin powers for an hour and thought it should be working out of the box.

This is issue is noticeable in our blazor app and our maui blazor hybrid mobile app.

We tried adding a middleware in identity service to replace the claims by the current role claims but it didn't work.

Do you have any suggestions?

Hi! We're preparing to go live soon—do you have an ETA on when this might be resolved? Thanks in advance!

okay thank you, will wait for an update, have a good day!