This problem has resolved. No response from your side since last 5 days so I tried with identityServer4 but using identityServer4 another issue came (upon login keeps redirecting back to login page and doesn't go to next page (HomeController -> Index page)). The ticket is open for this issue (https://support.aspnetzero.com/QA/Questions/11996/ASPNET-Zero-Upgrade-from-620-to-1311) please provide a solution for identityServer4 .
So switching to identityServer4 and then come back to OpenIdDict, now value is coming in ImpersonatorUserId.
we tried to stay at EF Core 2.1 without downgrade ABP packages (we cannot downgrade ABP packages because we are upgrading) but another exception comes as I have mentioned above in solution tried section and project doesn't run.
Is there any other solution other than fix queries?
Hi
I checked the logs but no error found. I think the problem is with Authorization. When I remove [AbpMvcAuthorize] from controller it goes to HomeController.
Hi @ismcagdas
We have tried with IdentityServer4 by installing latest version of IdentityServer4 and commented all OpenIdDict related code. The problem is upon login keeps redirecting back to login page and doesn't go to next page (HomeController -> Index page). Tried with clear caches, cookies etc. but no success. Receiving suscceed response from SignInManager but keeps redirecting back to login page.
Installing Packages:
LoadStop.Core Project: Abp.ZeroCore.IdentityServer4.EntityFrameworkCore Version="9.2.2"
LoadStop.Web.Core Project: Abp.ZeroCore.IdentityServer4 Version="8.4.0" IdentityServer4.AccessTokenValidation Version="3.0.1"
Hi Team, please respond.
Here is nuget packages(with versions) at *.EntityFrameworkCore project.
I have tried with disable OpenIddict but still issue persists. After debug get to know PrincipalAccessor in ClaimsAbpSession getting all claims except ImpersonatorUserId claim in PrincipalAccessor.
Yes token are generating successfully and found in cache as well. We are using OpenIdDict.
Development time. As we are upgrading
Issue resolved by Adding .AddFacility<LoggingFacility> in Startup.cs file.
Thanks @ismcagdas
