- ABP Framework version: v5.3.x
- UI type: Blazor Server
- DB provider: EF Core \
- Tiered (MVC) or Identity Server Separated (Angular): yes
- Exception message and stack trace: Could not find IdentityClientConfiguration for AbpMvcClient. Either define a configuration for AbpMvcClient or set a default configuration. [23:31:00 INF] Authorization failed. These requirements were not met: PermissionRequirement: ...
- Steps to reproduce the issue:" Run the application. Occasionally, the UI as well as some Menu items does not render. after a few minutes or refreshes, it may resolve to normal The issue happens both in developments (all apps in same box) and prod ( 1 box per each app - IDS, Blazor Server WAF, Web API)
We disabled Redis (ie not using) We have seen the threads: https://support.abp.io/QA/Questions/2633/Could-not-find-IdentityClientConfiguration-for-AbpMvcClientWhy and https://support.abp.io/QA/Questions/1627/How-can-I-persist-ASPNET-Core-Data-Protection-Keys-to-the-database
Both do not provide enough details to be conclusive.
Could you let us know what may be the root cause of the issue? Is it possibly because we are not using Redis ?
Thanks.
3 Answer(s)
-
0
Hi,
Is it possibly because we are not using Redis ?
For the Tiered project, you must use the distributed cache, like Redis.
-
0
To be clear, is it a distributed cache problem, whereas we need to have a central cache location otherwise permission can be lost. Or is it a data protection concern, whereas the keys need to be cached on a shared drive or a caching provider like Redis?
please clarify.
-
0
To be clear, is it a distributed cache problem, whereas we need to have a central cache location otherwise permission can be lost.
Distributed cache means that all applications use the same cache server, It's what you call “central cache”
Or is it a data protection concern, whereas the keys need to be cached on a shared drive or a caching provider like Redis
We cache data such as permission settings to improve performance, if you disabled the Redis, it will use memory cache by default, it will cause projects cache inconsistencies, so that is why you must use a distributed cache.
