Starts in:
2 DAYS
6 HRS
14 MIN
0 SEC
Starts in:
2 D
6 H
14 M
0 S

Activities of "serhatuysal"

I think I noticed something: when I included the source code of the module in the Angular project with 'abp add-module Volo.Identity.Pro', the 'log in with this user' button appeared, but when I installed the original '@volo/abp.ng.identity': '~8.3.0', it doesn't show up. I'm not sure if there's an issue with the library.

I tried the Layered Authentication Server in both a separated and a non-separated project, but the same issue occurred. :(

Yes, I know it won't appear for the admin user, but in the scenario you mentioned, it's not appearing either. I forgot to mention that earlier.

The logged-in user is an admin, and the 'Impersonation' permission appears to be active in the role settings.

  • ABP Framework version: v8.3.0
  • UI Type: Angular
  • Database System: EF Core (SQL Server)
  • Tiered Auth Server Separated (for Angular): yes/no
  • Exception message and full stack trace:
  • Steps to reproduce the issue:

I created a new ABP project and ran it without making any configuration changes, but the "Log in with this user" button is not visible. I would appreciate your assistance in identifying what settings or configurations I should check to resolve this issue.

Can you share your email address and I will send you remote connection information?

Can you please connect via remote desktop?

Angular project or InsanKaynaklari.HttpApi.Host project? Do you have a remote connection and review status? The project needs to be completed quickly. please

2024-09-19 08:16:52.688 +03:00 [INF] Request starting HTTP/1.1 POST http://iktest...tr/api/api/app/home/yayinda-olan-ilan-listesi - null 0 2024-09-19 08:16:52.688 +03:00 [INF] CORS policy execution successful. 2024-09-19 08:16:52.710 +03:00 [INF] Executing endpoint 'InsanKaynaklari.Homes.HomeAppService.yayindaOlanIlanListesi (InsanKaynaklari.Application)' 2024-09-19 08:16:52.710 +03:00 [INF] Route matched with {action = "yayindaOlanIlanListesi", controller = "Home", area = "", page = ""}. Executing controller action with signature System.Threading.Tasks.Task1[System.Collections.Generic.List1[InsanKaynaklari.Ilans.YayindakiIlanDto]] yayindaOlanIlanListesi() on controller InsanKaynaklari.Homes.HomeAppService (InsanKaynaklari.Application). 2024-09-19 08:16:52.710 +03:00 [WRN] The provided antiforgery token was meant for a different claims-based user than the current user. 2024-09-19 08:16:52.711 +03:00 [INF] Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'. 2024-09-19 08:16:52.711 +03:00 [INF] Executing StatusCodeResult, setting HTTP status code 400 2024-09-19 08:16:52.711 +03:00 [INF] Executed action InsanKaynaklari.Homes.HomeAppService.yayindaOlanIlanListesi (InsanKaynaklari.Application) in 0.5579ms 2024-09-19 08:16:52.711 +03:00 [INF] Executed endpoint 'InsanKaynaklari.Homes.HomeAppService.yayindaOlanIlanListesi (InsanKaynaklari.Application)' 2024-09-19 08:16:52.718 +03:00 [INF] Request finished HTTP/1.1 POST https://iktest...tr/api/api/app/home/yayinda-olan-ilan-listesi - 400 0 null 29.8056ms

  • ABP Framework version: v8.1.0

  • UI Type: Angular

  • Database System: EF Core (SQL Server)

  • Tiered (for MVC) or Auth Server Separated (for Angular): yes

  • Exception message and full stack trace:

  • Steps to reproduce the issue:

  • Hello,

    After publishing an Angular project to IIS in the production environment, when the resolution width is smaller than 1200px, POST, PUT, and DELETE requests return a Bad Request (400) error. Only GET requests return 200. However, when the resolution is larger than 1200px, the application works without any issues.

Showing 21 to 30 of 33 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06