Hi,
You can configure the AbpAspNetCoreAuditingOptions to ignore the hangfire URL: https://docs.abp.io/en/abp/latest/Audit-Logging#abpaspnetcoreauditingoptions
Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'.
Can you try using HTTPS?
Hi,
You can check the document: https://docs.abp.io/en/commercial/latest/startup-templates/microservice/interservice-communication
Hi,
You can check the unit tests: https://github.com/abpframework/abp/blob/dev/framework/test/Volo.Abp.Dapper.Tests/Volo/Abp/Dapper/Repositories/PersonDapperRepository_Tests.cs#L14
Hi,
You can update the IndexModel
class:
public class IndexModel : ....
{
public IActionResult OnGet()
{
if(!CurrentUser.IsAuthenticated)
{
return RedirectToPage("/Account/Login");
}
return Page();
}
}
Hi,
I'm not an openid expert You can get help from openiddict: https://github.com/openiddict/openiddict-core/issues
however in the 'Module' template type's generated code there is a .WebAssembly project. So I'll ask again, what is the purpose of this project type and more importantly why is it not mentioned anywhere in the documentation
I will update the document.
When you create a module project, you may want it to support both Blazor WebAssembly and Blazor Server. because the details may be different when writing UI code. , so ABP has created separate projects for them.
Anyway, you can remove it if you don't need it.
Yes, it's normal.
You can see: https://github.com/openiddict/openiddict-core/issues/1394
Let me explain more.
To get access_token, Blazor WebAssembly and Blazor Server are different.
In Blazor WebAssembly
[Inject]
protected IAccessTokenProvider AccessTokenProvider { get; set; }
var token = await AccessTokenProvider.RequestAccessToken();
In Blazor Server
[Inject]
protected IHttpContextAccessor HttpContextAccessor { get; set; }
var token = HttpContextAccessor.HttpContext.GetTokenAsync("access_token");