I tested with QA team against our QA site, we noticed when we click submit security code at the same time, it's much easy to reproduce. This issue becomes our upgrade blocker. Could we have a session to debug?
Even a success login, the home search page flash 2+ times, looks like go to auth server again and back to home page
After upgrade to 9.1.3, the error is still there. It happens when make connect/authorize Url, I did Url decoding and Html decoding to the Url, it looks like this, I feel like the Url is extremely long and duplicate connect
https://ca.authserver.host/connect/authorize?response_type=code&client_id=Angular&state=azU5cEs1Sk9Ua2JTcm1aVHlzaExiWjZrQXpqNUhxUVNNQUpsNDc1NXlKN2VR;/home/es-search?code=FbCK06zR-ZE3xt7LplqKFuOFVxuwjbgnqJobXC4z2v4&state=QVViSjhnd1VGWGFGQ3JjRFo3aExxTEZfdjNhR1VkTGp6MzBnYjhacTV3Rmp6;%252Fhome%252Fsearch%253Fcode%253DfVFNO5CT4ozUXn3SWbWF3Yx_vRmv8z8g9luGtz-jOCM%2526state%253DMzY3N2ZRV2F3UGNtNTlkbXQ1NWtyNUtTeXFKMlRpRXV1b1dWd3djWUwxdzdK%253B%2525252Fhome%2525252Fes-search%2526iss%253Dhttps%253A%25252F%25252Fca.authserver.host%25252F%2526culture%253Den%2526ui-culture%253Den&iss=https:%2F%2Fca.authserver.host%2F&culture=en&ui-culture=en&redirect_uri=https://ca.ess-portal.host/&scope=offline_accessopenidprofileemailphoneAccountServiceIdentityServiceAdministrationServiceSaasServiceEntityServiceSearchServiceLookupServiceAuditServiceDashboardService&code_challenge=cl1auIiaHiVaQMiBpDPk2OMIAccR0P9wJa2mOZMdG5w&code_challenge_method=S256&nonce=azU5cEs1Sk9Ua2JTcm1aVHlzaExiWjZrQXpqNUhxUVNNQUpsNDc1NXlKN2VR&culture=en&ui-culture=en&returnUrl=/home/search?code=FbCK06zR-ZE3xt7LplqKFuOFVxuwjbgnqJobXC4z2v4&state=QVViSjhnd1VGWGFGQ3JjRFo3aExxTEZfdjNhR1VkTGp6MzBnYjhacTV3Rmp6;%2Fhome%2Fes-search%3Fcode%3DfVFNO5CT4ozUXn3SWbWF3Yx_vRmv8z8g9luGtz-jOCM%26state%3DMzY3N2ZRV2F3UGNtNTlkbXQ1NWtyNUtTeXFKMlRpRXV1b1dWd3djWUwxdzdK%3B%25252Fhome%25252Fes-search%26iss%3Dhttps%3A%252F%252Fca.authserver.host%252F%26culture%3Den%26ui-culture%3Den&iss=https://ca.authserver.host/&culture=en&ui-culture=en
I upgrade the front-end code to exactly version of '9.1.3', I also update backend to 9.1.3. The 409 still happens. Is there a way to swallow this 409 error either from front-end or backend?
The code use to use '~9.1.1', if I check the lock file, it does install 9.1.3. If I use exact version 9.1.1 or 9.1.2, it will have null DI exception. Now I change to use exact version '9.1.3' the DI exception is gone.
However, the console error in the beginning of this ticket is still there.
hi
Please share full debug logs.
Are you sure all your packages are 9.1.1? You can try to upgrade to the latest 9.1.3 https://www.nuget.org/packages/Volo.Abp.Cli/9.1.3
Thanks.
I couldn't upgrade to 9.1.2, create a separate ticket here: https://abp.io/support/questions/9348/ABP-9-upgrade
Here is part of package.json "@abp/ng.components": "~9.1.1", "@abp/ng.core": "~9.1.1", "@abp/ng.oauth": "~9.1.1", "@abp/ng.setting-management": "~9.1.1", "@abp/ng.theme.shared": "~9.1.1", "@abp/ng.feature-management": "~9.1.1", "@volo/abp.commercial.ng.ui": "~9.1.1", "@volo/abp.ng.account": "~9.1.1", "@volo/abp.ng.audit-logging": "~9.1.1", "@volo/abp.ng.identity": "~9.1.1", "@volo/abp.ng.language-management": "~9.1.1", "@volo/abp.ng.openiddictpro": "~9.1.1", "@volo/abp.ng.saas": "~9.1.1", "@volo/abp.ng.text-template-management": "~9.1.1", "@volosoft/abp.ng.theme.lepton-x": "~4.1.1", "@angular/animations": "~19.1.0", "@angular/cdk": "~19.1.0", "@angular/common": "~19.1.0", "@angular/compiler": "~19.1.0", "@angular/core": "~19.1.0", "@angular/forms": "~19.1.0", "@angular/localize": "~19.1.0", "@angular/material": "~19.1.0", "@angular/material-date-fns-adapter": "~19.1.0", "@angular/platform-browser": "~19.1.0", "@angular/platform-browser-dynamic": "~19.1.0", "@angular/router": "~19.1.0",
yarn version 1.22.22
export const appConfig: ApplicationConfig = { providers: [ provideAppInitializer(appInitializerFactory()), importProvidersFrom([ AccountAdminConfigModule, IdentityConfigModule, ThemeLeptonXModule.forRoot(), SideMenuLayoutModule.forRoot(), AccountLayoutModule.forRoot(), ]), provideRouter(appRoutes), APP_ROUTE_PROVIDER, OVERRIDE_LEPTON_X_USER_MENU_PROVIDERS, provideAnimations(), // Add the date-fns adapter provider - this is the correct way in Angular 19 provideDateFnsAdapter(), provideAbpCore( withOptions({ environment, registerLocaleFn: registerLocale(), }), ), provideAbpOAuth(), provideOpeniddictproConfig(), provideIdentityConfig(), provideSettingManagementConfig(), provideFeatureManagementConfig(), provideAccountAdminConfig(), provideTextTemplateManagementConfig(), provideLanguageManagementConfig(), provideAccountPublicConfig(), provideCommercialUiConfig(), provideAuditLoggingConfig(), ACCOUNT_MANAGE_PROFILE_TAB_PROVIDERS, //This is local's override abp provider AuditInterceptorProvider, provideAbpThemeShared( withHttpErrorConfig({ errorScreen: { component: HttpErrorComponent, forWhichErrors: [401, 403, 404, 500], hideCloseIcon: true, }, }), withValidationBluePrint({ wrongPassword: 'Please choose 1q2w3E*', }), ), provideSaasConfig(), DateFnsFormatDateTimePipe, DatePipe, TitleCasePipe,
], };
Here is from log: [20:16:42 INF] Executed action method Volo.Abp.OpenIddict.Controllers.AuthorizeController.HandleAsync (Volo.Abp.OpenIddict.AspNetCore), returned result Microsoft.AspNetCore.Mvc.SignInResult in 83.8041ms. [20:16:42 INF] Executing SignInResult with authentication scheme (OpenIddict.Server.AspNetCore) and the following principal: System.Security.Claims.ClaimsPrincipal. [20:16:42 WRN] There is an entry which is not saved due to concurrency exception: OpenIddictAuthorization {Id: 8b3fde63-5710-65fd-c036-3a135d4249bc} Modified FK {ApplicationId: 55abca09-b50d-399f-246c-3a0cbf31440d}
[20:16:42 INF] Executed action Volo.Abp.OpenIddict.Controllers.AuthorizeController.HandleAsync (Volo.Abp.OpenIddict.AspNetCore) in 120.0721ms [20:16:42 INF] Executed endpoint 'Volo.Abp.OpenIddict.Controllers.AuthorizeController.HandleAsync (Volo.Abp.OpenIddict.AspNetCore)' [20:16:42 WRN] There is an entry which is not saved due to concurrency exception: OpenIddictAuthorization {Id: 8b3fde63-5710-65fd-c036-3a135d4249bc} Modified FK {ApplicationId: 55abca09-b50d-399f-246c-3a0cbf31440d}
[20:16:42 ERR] An unhandled exception has occurred while executing the request. Volo.Abp.Data.AbpDbConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See https://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimistic concurrency exceptions. ---> Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: The database operation was expected to affect 1 row
This error comes back again. After yesterday's deployment, there is no 409 error. And this noon, I access QA site again (no new deployment) since that. Is it because of something regarding to session expired
