Looks like there's something wrong with your HTTPS certificate.
https://devblogs.microsoft.com/dotnet/configuring-https-in-asp-net-core-across-different-platforms/ https://www.google.com/search?q=free+ssl+certificate
hi
My timezone is UTC+8
https://www.worldtimebuddy.com/event?lid=1816670&h=1816670&sts=28255200&sln=10-18&a=preview
hi
I checked the code and everything works as expected.
Can you publish this project to iis or another environment?
and deployed it here: https://kog-vanilla-blazor.azurewebsites.net/ https://kog-vanilla-api.azurewebsites.net/
hi
Thanks. I will check the code.
You don't seem to refer to the code I shared.
You should first authenticate the user and then issue cookies. The cookies should contain correct user information, not a Login claim. Then, try to authenticate the cookies in the middleware.
hi
You don't need to refer to the current implementation. You don't need to use CreatePermissionGroupDefinitions and Lazy<Dictionary<string at all.
You can maintain a collection by yourself.
hi
You can replace the FakeCurrentPrincipalAccessor in ConfigureServices method.
https://github.com/abpframework/abp/blob/dev/framework/test/Volo.Abp.AspNetCore.Mvc.Tests/Volo/Abp/AspNetCore/Mvc/Auditing/AuditIntegrationServiceTestController_Tests.cs#L28
Create a new class by copying the code form AbpValidateClientPostLogoutRedirectUri
Add your class to event handles.
builder.RemoveEventHandler(OpenIddictServerHandlers.Session.ValidateClientPostLogoutRedirectUri.Descriptor);
builder.RemoveEventHandler(AbpValidateClientPostLogoutRedirectUri.Descriptor);
builder.AddEventHandler(MyAbpValidateClientPostLogoutRedirectUri.Descriptor);
The StaticPermissionDefinitionStore is ISingletonDependency
You can inject it and use it anywhere. Use your logic to control PermissionDefinitions
hi
You can troubleshoot by creating a new template project and deploying it to the production environment to see if the problem exists.
If the problem doesn't exist,please compare the code or share your project with me.
Thanks
