Activities of "vkelwan"

Hi,

We have identified and resolved the issue.

Investigation: As per your suggestion, we temporarily removed AbpCachingStackExchangeRedisModule from Administration service to test with in-memory cache.

After that change, the Administration service started calling: POST https://auth.activitylinker.com/api/account/dynamic-claims/refresh on every request. AuthServer returned 204 OK but Administration service threw: "Failed to refresh remote dynamic claims cache for user"

This was causing a continuous redirect loop on every page load.

Fix Applied: We set WebRemoteDynamicClaimsPrincipalContributorOptions.IsEnabled = false in TMSMSAdministrationServiceModule.cs:

public override void PreConfigureServices(ServiceConfigurationContext context) { PreConfigure<WebRemoteDynamicClaimsPrincipalContributorOptions>(options => { options.IsEnabled = false; }); }

After this change redirect loop stopped and login works correctly.

We have also sent you an email at liming.ma@volosoft.com from neel.m@technoheaven.net with the logs captured after removing AbpCachingStackExchangeRedisModule. Please check your email for the attached log file.

Questions:

  1. Is this the correct permanent fix or just a workaround?
  2. Should we keep AbpCachingStackExchangeRedisModule removed or add it back?
  3. What is the proper way to enable remote dynamic claims in our microservice setup?

Thanks, Neel Kotadia Techno Heaven

Hello, I have changed in a TMSMSAdministrationServiceModule.cs but after this i am getting this issue.

[08:40:35 WRN] The cookie 'XSRF-TOKEN' has set 'SameSite=None' and must also set 'Secure'. [08:40:35 DBG] Executing AbpApplicationConfigurationAppService.GetAsync()... [08:40:35 DBG] Executed AbpApplicationConfigurationAppService.GetAsync(). [08:40:35 INF] Executing ObjectResult, writing value of type 'Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.ApplicationConfigurationDto'. [08:40:35 INF] Executed action Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationConfigurationController.GetAsync (Volo.Abp.AspNetCore.Mvc) in 66.8065ms [08:40:35 INF] Executed endpoint 'Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationConfigurationController.GetAsync (Volo.Abp.AspNetCore.Mvc)' [08:40:35 INF] Request finished HTTP/1.1 GET http://adminserver/api/abp/application-configuration?includeLocalizationResources=false - 200 null application/json; charset=utf-8 100.208ms [08:40:35 INF] Request starting HTTP/1.1 GET http://adminserver/api/abp/application-localization?cultureName=en&onlyDynamics=false - null null [08:40:35 INF] CORS policy execution successful. [08:40:35 DBG] Get dynamic claims cache for user: 0e3c4557-57fd-31b4-7781-3a1df656b05c [08:40:35 DBG] Refresh dynamic claims for user: 0e3c4557-57fd-31b4-7781-3a1df656b05c from remote service. [08:40:35 INF] Start processing HTTP request POST https://auth.activitylinker.com/api/account/dynamic-claims/refresh [08:40:35 INF] Sending HTTP request POST https://auth.activitylinker.com/api/account/dynamic-claims/refresh [08:40:35 INF] Received HTTP response headers after 23.7656ms - 204 [08:40:35 INF] End processing HTTP request after 23.8603ms - 204 [08:40:35 WRN] Failed to refresh remote dynamic claims cache for user: 0e3c4557-57fd-31b4-7781-3a1df656b05c Volo.Abp.AbpException: Failed to refresh remote claims for user: 0e3c4557-57fd-31b4-7781-3a1df656b05c at Volo.Abp.Security.Claims.RemoteDynamicClaimsPrincipalContributorCacheBase1.GetAsync(Guid userId, Nullable1 tenantId) at Volo.Abp.Security.Claims.RemoteDynamicClaimsPrincipalContributorBase2.ContributeAsync(AbpClaimsPrincipalContributorContext context) [08:40:35 INF] Executing endpoint 'Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationLocalizationController.GetAsync (Volo.Abp.AspNetCore.Mvc)' [08:40:35 INF] Route matched with {area = "abp", action = "Get", controller = "AbpApplicationLocalization", page = ""}. Executing controller action with signature System.Threading.Tasks.Task1[Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.ApplicationLocalizationDto] GetAsync(Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.ApplicationLocalizationRequestDto) on controller Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationLocalizationController (Volo.Abp.AspNetCore.Mvc). [08:40:35 INF] Executing ObjectResult, writing value of type 'Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.ApplicationLocalizationDto'. [08:40:35 INF] Executed action Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationLocalizationController.GetAsync (Volo.Abp.AspNetCore.Mvc) in 6.8293ms [08:40:35 INF] Executed endpoint 'Volo.Abp.AspNetCore.Mvc.ApplicationConfigurations.AbpApplicationLocalizationController.GetAsync (Volo.Abp.AspNetCore.Mvc)' [08:40:35 INF] Request finished HTTP/1.1 GET http://adminserver/api/abp/application-localization?cultureName=en&onlyDynamics=false - 200 null application/json; charset=utf-8 34.1723ms [08:40:37 DBG] Executing HealthCheck collector HostedService. [08:40:37 INF] Start processing HTTP request GET http://[::]/health-status [08:40:37 INF] Sending HTTP request GET http://[::]/health-status [08:40:37 ERR] GetHealthReport threw an exception when trying to get report from /health-status configured with name AdministrationService Health Status. System.Net.Http.HttpRequestException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName') ([::]:80) ---> System.ArgumentException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName') at System.Net.Dns.GetHostEntryOrAddressesCoreAsync(String hostName, Boolean justReturnParsedIp, Boolean throwOnIIPAny, Boolean justAddresses, AddressFamily family, CancellationToken cancellationToken) at System.Net.Sockets.Socket.ConnectAsync(SocketAsyncEventArgs e, Boolean userSocket, Boolean saeaCancelable) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ConnectAsync(Socket socket, Boolean saeaCancelable) at System.Net.Sockets.Socket.ConnectAsync(EndPoint remoteEP, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) --- End of inner exception stack trace --- at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.InjectNewHttp11ConnectionAsync(QueueItem queueItem)

Hello,

We have sent the full Administration service debug logs to your email (liming.ma@volosoft.com) from neel.m@technoheaven.net with the subject "Slow response time of application-configuration during login".

Please check the email for the attached logs.

Thanks, Neel Kotadia

But on every time on page load also this call takes 2-3 secs

We are experiencing significant delay during user login due to a slow response from the following API:

/api/abp/application-configuration?includeLocalizationResources=false

This API call is taking longer than expected and is impacting the overall login performance and user experience. Observed Behavior

  • The API call consistently takes longer than expected.
  • This results in delayed application loading after login.
  • The issue is reproducible across multiple attempts.

Expected Behavior

  • The API should respond within an acceptable time (ideally under 500 ms).
  • The login and application initialization process should be smooth and fast.

Attachments

Please find the relevant screenshots below demonstrating the issue:

We already Run the Migrations for Both PostGres service and MongoDb Service. Also there is no option to provide permissions for role or user and also not appear in the database.

We also take reference from community post and also check sample code given in repository, but it did not helped me in sorting this out.

So help me.

Environment Information:
• ABP Framework Version: (9.2.0)
• UI Type: Angular
• Database (Main App): SQL Server
• New Microservice Databases: PostgreSQL
• Solution Type: Microservice
• Auth Server Type: IdentityServer
• 

Problem Description: I'm adding a new microservice to an existing ABP.IO microservice solution (created with abp new using SQL Server). The new service uses: • PostgreSQL for relational data (via EF Core) While the backend API for the new microservice builds and runs, it is not integrated properly into the solution:

Issues Encountered: 1. Backend API not visible in Angular UI ◦ API endpoints are functional (tested with Swagger) ◦ Angular app does not show menus or modules related to the new microservice 2. No Permissions Created ◦ Permission groups defined in the new microservice are not visible in the AbpPermissions table in SQL Server ◦ No roles or permissions appear to be synchronized 3. Settings Not Registered ◦ Settings defined in the new microservice module are not persisted to the database ◦ They don't appear in the AbpSettings table 4. No Navigation/Menu Integration ◦ Angular does not list the new module/menu ◦ Menu contributor not picked up (even though it’s implemented)

And For MongoDB Service

Environment Information: • ABP Framework Version: (9.2.0) • UI Type: Angular • Database (Main App): SQL Server • New Microservice Databases: MongoDB • Solution Type: Microservice • Auth Server Type: IdentityServer • Problem Description: I'm adding a new microservice to an existing ABP.IO microservice solution (created with abp new using SQL Server). The new service uses: • MongoDB While the backend API for the new microservice builds and runs, it is not integrated properly into the solution:

Issues Encountered: 1. Backend API not visible in Angular UI ◦ API endpoints are functional (tested with Swagger) ◦ Angular app does not show menus or modules related to the new microservice 2. No Permissions Created ◦ AbpPermissions documents are created in MongoDB database, not in SQL Server (Is that correct?) ◦ Permission groups defined in the new microservice are not visible in the AbpPermissions Document in MongoDB. ◦ No roles or permissions appear to be synchronized 3. Settings Not Registered ◦ Settings defined in the new microservice module are not persisted to the database ◦ They don't appear in the AbpSettings Document in MongoDB. 4. No Navigation/Menu Integration ◦ Angular does not list the new module/menu ◦ Menu contributor not picked up (even though it’s implemented)

Showing 51 to 57 of 57 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v11.1.0-preview. Updated on November 20, 2026, 13:33
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.