Activities of "markusbergkvist"

I have downgraded and it worked fine, thanks! We have used 1.6.2 since the upgrade to 9.0 but for some reason icons started acting wierd and we tried upgraded to 1.7.6 which broke other icons.

We'll use 1.6.2 from now on.

Hi, thanks for the reply. We did not have the "Send confirmation mail" checkbox:

After trying different settings we now understand that "Require confirmed email" in Administration/Settings/Identity Management is required to be checked for this feature to be enabled at all, maybe this could be clarified some way, we may do a pull request on this. Thanks again!

While we are working on this, could you please answer what emailing features we can expect work out of the box from the identity module beside the forgot password link email? For instance, should the new user get a "confirm email" on created if we dont check the "Email confirmed" box?

Hi, adding typeof(SaasHostApplicationModule) to the ApplicationModule solved the issue, we now see it probably was mistakenly deleted in the process of reverting to the nuget package. Thanks!

Hi, I have tried to reproduce the error as well, without success. I will continue to try to find the issue why this is happening in our specific project, I will get back to you regarding this if there are any progress. Thanks for your help!

Hi, Without Mailkit installed, no. With MailKit installed, yes.

Hello, The temporary solution you suggested seems to work, thanks for your help!

Ok, thank you, let us know about the progress when possible, our project progress is on hold while we cant solve this.

Thanks again

Hi,

Thank you for your suggestions. We have tried both configurations you provided:

1. Using PreConfigure<ISignalRServerBuilder>:

   PreConfigure<ISignalRServerBuilder>(builder =>
   {
       builder.AddAzureSignalR(options =>
       {
           options.ConnectionString = context.Services.GetConfiguration().GetConnectionString("AzureSignalR");
           options.ServerStickyMode = Microsoft.Azure.SignalR.ServerStickyMode.Required;
       });
   });
   

2. Using context.Services.AddSignalR with filters:

   context.Services.AddSignalR(options =>
   {
       options.DisableImplicitFromServicesParameters = true;
       options.AddFilter<AbpHubContextAccessorHubFilter>();
       options.AddFilter<AbpAuthenticationHubFilter>();
       options.AddFilter<AbpAuditHubFilter>();
   }).AddAzureSignalR(options =>
   {
       options.ConnectionString = context.Services.GetConfiguration().GetConnectionString("AzureSignalR");
       options.ServerStickyMode = Microsoft.Azure.SignalR.ServerStickyMode.Required;
   });
   

Unfortunately, neither of these resolved the issue of HttpContext being null when Azure SignalR is configured.

We have found two related issues with Azure SignalR disrupting the httpcontext:

• GitHub Issue: dotnet/aspnetcore#17617
• StackOverflow Discussion: Azure SignalR Service: HttpContext null

Since Abp is relying on httpcontext in the BlazorServerLookupApiRequestService we either need an alternate solution to setting the headers or possibly a way to configure azure signalr so that we still have access to the httpcontext if that still is the issue.

Thank you for your assistance

We have not deployed to Azure yet, so this issue is occurring in our local development environment. Therefore, Azure-specific settings like enabling WebSockets should not be related to the problem.