Hi, can you please check if your problem is the same as in this issue (https://github.com/abpframework/abp/issues/10929)?
Hi, the Text Template Management module in ABP Framework supports tenant-specific and culture-specific template customizations out of the box.
However, implementing role-based customization requires more extensive changes. For example, you would need to:
AbpTextTemplateContents table to include a RoleId column,Since this involves updating several layers (from database to application logic), it’s not straightforward to list all required changes here. We recommend checking the Text Template Management module's source code to identify the key integration points and customize the behavior based on your needs.
Regards.
context.Services.AddIdentity<IdentityUser, IdentityRole>() .AddEntityFrameworkStores<CoreBackendDbContext>() .AddDefaultTokenProviders();
Hi, you don't need to add this configuration, if your project depends on the Volo.Abp.Identity.Pro.Domain project, then there is a similar configuration is already made on the module side. So, you can remove this configuration. Probably, it's causing this problem because it overrides the default registration:
context.Services.AddIdentityCore<IdentityUser>().AddTokenProvider(TokenOptions.DefaultAuthenticatorProvider, typeof(AbpAuthenticatorTokenProvider));
Therefore, can you please remove the related configuration in your side, and check if it fixes the problem or not?
[merdan] said: Ok, thanks for the clarification. Am I right to think that startup templates don't change on patch releases (like in my case, between 9.1.1 and 9.1.3), so I can just update ABP packages and keep other files as is?
Yes, in patch releases we only fix bugs, and typically you don't need to change any file. You can directly switch to stable and continue developing.
Regards.
Hi, while you are checking the Redis Server and fixing the overload problem, do you need anything from our side?
[dhaoo] said: Must the interface defined by *.Application.Contracts be referenced in the module to implement the proxy? Is it referenced in the *.HttpApi project or in the *.httpapi.client
Yes, we suggest defining in a shared library between client and secret, so you can use the application service interface in your client application and generate a proxy for that. (https://abp.io/docs/latest/framework/api-development/static-csharp-clients#service-interface)
Otherwise, you might need to create a httpclient instance yourself, and send a request to the related service endpoint manually. Please refer to https://abp.io/docs/latest/framework/api-development/static-csharp-clients#service-interface for more information.
Regards.
[sahanaacharya] said: Hi,
Thanks for the quick response. Could you please let us know which service has the gdpr data. i was unable to find it in administration service.
Sorry, I'm not sure that I've understood it correctly. Can you please explain it in detail? Do you mean the administration service in the microservice solution or something else?
Hi, personal data preparation endpoint is -> /api/gdpr/requests/prepare-data
Btw, in development environment, you can open Swagger and find the GdprRequest section to see all endpoints provided by the GDPR Module:
Regards.
I've customized the login page with your default.cshtml file but unable to reproduce your problem. Please share your solution via email to support@abp.io with ticket number, so I can directly check from your project.
Regards.
[LW] said: Yes, we are using Redis already. My initial thought was that it cannot be the Redis, since we see no overload indicators in Azure Redis monitoring. However we see some intermittent timeout exceptions and in those I can see, if I understand correctly, some pretty high number of waiting calls (async-ops count), which could indicate some Redis overload.
Timeout awaiting response (outbound=0KiB, inbound=0KiB, 5859ms elapsed, timeout is 5000ms), command=EXPIRE, next: EXPIRE c:Volo.Abp.MultiTenancy.TenantConfiguration,k:SCM_PROD:i:dba2a1ba-5a58-f4f6-ec6a-3a03f2c223b2,n:null, inst: 0, qu: 0, qs: 0, aw: False, bw: SpinningDown, rs: DequeueResult, ws: Idle, in: 0, last-in: 0, cur-in: 63, sync-ops: 19115, **async-ops: 1215359**, serverEndpoint: redis-paas-PROD-002.redis.cache.windows.net:6380, conn-sec: 27571.89, aoc: 0, mc: 1/1/0, mgr: 9 of 10 available, clientName: AW0SDWK000002(SE.Redis-v2.7.27.49176), IOCP: (Busy=0,Free=1000,Min=1,Max=1000), WORKER: (Busy=30,Free=32737,Min=2,Max=32767), POOL: (Threads=30,QueuedItems=4,CompletedItems=3836531,Timers=54), v: 2.7.27.49176 (Please take a look at this article for some common client-side issues that can cause timeouts: https://stackexchange.github.io/StackExchange.Redis/Timeouts)
This might be the reason. If the cache response doesn't arrive within a specific time, the data will be retrieved from the database instead.
