Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC
Open Closed

Problems with version 8 and core 3.0 for an already created project #8018


User avatar
0
unidata created

Hello! First of all I wanted to congratulate you on the product, I have been using ABP a year ago and it seemed so good that it is worth moving to the commercial version, AspNetZero. I acquired a license 25 days ago and created a project and downloaded it. At that time the project was in Asp.Net Core & Angular v7.2.3 and .Net Core 2.2. I saw that the new version, v8.0, came out with support for .Net Core 3.0. But when I want to download the project I only see that I can download version v8.0 but for .Net Core 2.2. I download it and see that indeed all projects point to .Net Core 2.2.

If I upgrade all projects to .Net Core 3.0, compile Ok and manual swagger tests work. But if there is the angular app it gives an error in the browser "InternalServerError". Log information is as follows:

Microsoft.IdentityModel.Tokens.SecurityTokenInvalidSignatureException: IDX10503: Signature validation failed. Keys tried: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.] '. Exceptions caught: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.] '. token: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.] '. at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature (String token, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken (String token, TokenValidationParameters validationParameters, SecurityToken & validatedToken) at VCloud.Web.Authentication.JwtBearer.VCloudJwtSecurityTokenHandler.ValidateToken (String securityToken, TokenValidationParameters validationParameters, SecurityToken & validatedToken) in D: \ Source \ Unidata \ ASPNetZero \ ASPNetZ-core \ ASPNetZero \ ASPNetZ-core \ ASPNetZ-core3 VCloud.Web.Core \ Authentication \ JwtBearer \ VCloudJwtSecurityTokenHandler.cs: line 40 at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync () INFO 2019-11-14 16: 46: 01,353 [24] uthentication.JwtBearer.JwtBearerHandler - Bearer was not authenticated. Failure message: IDX10503: Signature validation failed. Keys tried: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.] '. Exceptions caught: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.] '. token: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.] '. INFO 2019-11-14 16: 46: 01,354 [24] Microsoft.AspNetCore.Hosting.Diagnostics - Request finished in 3956.4738ms 404 DEBUG 2019-11-14 16: 46: 06,786 [19] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-11-14 16: 46: 12,285 [4] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-11-14 16: 46: 17,775 [4] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null DEBUG 2019-11-14 16: 46: 23,258 [4] HttpRequestEntityChangeSetReasonProvider - Unable to get URL from HttpRequest, fallback to null

Questions: 1-When downloading the project already created, it should not come already configured in .Net Core 3.? 2-Any idea why I have the error indicated?

One last point. I downloaded a demo project (v8.0.0, Aspnet core 3.0 + Angular) in a new database (the demo project IS configured for .net core 3.0 by default) and that project works perfectly for me.

I have been with this problem for several days and I can't find how to solve it This is my 3 post on the subject regards!!


2 Answer(s)
  • User Avatar
    0
    unidata created

    Update: Generate the project with the same name again and download it. This time it came configured with .net core 3 correctly, but still giving the same error from the angular application.

  • User Avatar
    0
    unidata created

    After many tests, regenerating the project, for some reason that I cannot determine, is already working correctly.

    Very strange since there were no changes in sources files or configuration, just recompile several times.