Hi, We are experiencing the following issue while running our system on IIS behind Cloudflare firewall: Abp.Localization.CultureName value being stripped off from the cookie header when we inspect server requests on the server using WireShark sniffer. We found similar ticket regarding ABP.TenantId and the solution of customizing the name of the cookie to remove dot character which is not allowed by Cloudflare. https://github.com/aspnetboilerplate/aspnetboilerplate/pull/4349. Is there a way to customize Abp.Localization.CultureName to prevent stripping off by the firewall. Thanks! We are using Angular +ASP.Net core v13
Hello,
When 2-factor authentication is enabled, the user enters their Username and Password and then completes 2-factor authentication.
Now, the issue is that the LoginAsync() method in AbpLogInManager, saves the success records in the ABPLoginAttempts table before verifying the 2FA code entered by the user.
So in the case where the username and Password are correct, but the 2FA code is incorrect, a user fails to log in, but the ABPLoginAttempts table shows success.
Here it just checks the Username/Password and saves the attempt as Success.
Hi, Is there an example of using Encryption middleware with GraphQL in Aspnet Zero for decrypting requests and encrypting responses?
Thanks!
While following the version update guide provided at https://docs.aspnetzero.com/en/common/latest/Version-Updating, I encountered issues during the migration of the API. The aspnetzero version 13 that I downloaded does not execute and lacks any imports, leading me to question if this was an intentional design choice. Currently, my project is experiencing over 12,000 file conflicts, primarily due to the removal of imports in version 13. Is this a typical scenario, and are we expected to resolve all these conflicts manually?
My team has encountered an issue where, despite the lockout duration expiring, users remain locked out according to the admin dashboard's user table, although login is possible. Could this be a bug within the framework, or is it possible that we are misconfiguring the user settings?
Hello, We've been seeing a lot of SignalR related errors in production environments: one of the most common issues is this request fails with response code 0. POST /signalr-chat/negotiate?enc_auth_token=wNYmO41%2F48SHNstaLVXxHCCre29BZQl1NhC6NM3R3rzpXtPQxVzH6jEzA%2FQhXFN5tu6Fk7pO53uppm1mVXMZgxbyRVz26dnepi%2FFyB6axBY%2B6gq1GL%2BuRQgoiFUCjRN2p8w6LevViwKlHyWZZJZO1DGVSjAi1m2U%2Bog9pkHw9%2FSxl3%2FCN5UQl0zWOAF1kZIOvFlT8rcg3PxdGPwFTMql9snkIL29UFtw7ie5BwWrOOXGeIpwMw7Q582asrU1E8G%2FwLcc7d38xTPFUCgSUVYrlUSdjC1wVJIMfTBdfVKxJVuLz%2FVKNqwGWSkISts00UySZwgoQT4HK4O0E0fnkOAdrcOwsbNP%2FvQuHXKpd7dNX%2FFA7V4MMCVGPzwYmQKsewZopNUtqtRJiyIKrO%2BaooXJ8%2FR6jz77s%2FqATwXK%2BQqcGWBA3LV5uhs%2FLNmPOjMZzARUPNc3ZbsTUPBsMyl2q7FV8cGlE4nw5KPJvtwOYXsMeyjqhdgbSXMntyTlywvrJRcEsS8t3qdbwuQkPVleeydZlKTs6J7BNYZzy8p3NeyeSEEgTQAZjQ%2B5zVnnmhNF3BdGpLsiCT3%2FZ3JdyrTSfFrhnptDPD6Ih3BfC2hTMmMA4OfhAfaTDUDpc88y3cxCn3kaXO%2BgIxuTdjU%2BZayNLFu8cNI5%2BYaQoLpDyavc5lUq7HwRX8p226CvDERJjDMNvyybye6UoZYnz%2BahBr3Uohi3zly000T5r%2B8oAvLxk3Marl5NaBwY0E0Q0N1HjtDn4o18QINsYs5ieyzK6%2FbzzbUu4G3L5V2FgTWNmnOWSPmaYP7BtdoWoItFXlptwpo4MHgmOvIe2f2hX0RKfXATsSfW2SMky1qoEDRpur6fe8ZXWnBkUIIg9LjfdFaVQwq7%2FUz
In the following article Microsoft mentions a way to configure SignalR to use only WebSocket and turn off Negotiation. What is the way to apply this in ASPNet Boilerplate? https://learn.microsoft.com/en-us/aspnet/core/signalr/scale?view=aspnetcore-7.0 Please advise Thanks
What is your product version?
What is your product type (Angular or MVC)?
What is product framework type (.net framework or .net core)?
What is ABP Framework version?
We have a requirement from client to make user first name non-mandatory I know that in asp.net zero this is a required field. I am trying to find a way but couldn't find a good solution from forums to do this with minimal changes. Is there a way, or a work around for this requirement?
Please answer the following questions before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
We have a deployment on Azure with scaled out enabled with 3 instances for Web API tier.
ARR (Affinity Cookie) configuration is enabled to allow all requiests to be directed to the same instance for a given user (sticky session) .
All the functionality works fine except for Impersonation. When admin user selects one of the other users to impersonate he gets an error:
"Abp.UI.UserFriendlyException: Impersonation token is invalid or expired! at PatientPortal.Authorization.Impersonation.ImpersonationManager.GetImpersonatedUserAndIdentity(String impersonationToken) in D:\a\1\s\src\PatientPortal.Core\Authorization\Impersonation\ImpersonationManager.cs:line 38 at PatientPortal.Web.Controllers.TokenAuthController.ImpersonatedAuthenticate(String impersonationToken) in D:\a\1\s\src\PatientPortal.Web.Core\Controllers\TokenAuthController.cs:line 346 at lambdamethod(Closure , Object ) at Microsoft.Extensions.Internal.ObjectMethodExecutorAwaitable.Awaiter.GetResult() at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at System.Threading.Tasks.ValueTask1.getResult() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() UserFriendlyException.Code:0 UserFriendlyException.Details:"
We use AbpMemoryCacheManager, and if every user requests hits the same appservice instance there should not be an issue.
Please share your experience with such issues
Thanks, Sergei
What is your product version?
What is your product type (Angular or MVC)?
What is product framework type (.net framework or .net core)?
What is ABP Framework version? (5.3.2)
How can I show the date exactly as it is from the database to the client without any timezone conversions?