Activities of "DominaTang"

We rolled back our QA site from ABP 9 to ABP8:

1. Restore database backup prier to ABP 9 upgrade
2. Deploy code back to ABP 8.2.3 version

However, when login page, it keeps giving us 500 error in login page, from exception below, obviously in ABP 9 these columns are dropped, but ABP 8 table has it. We check the code deployed to app container, the ABP version is 8.2.3. We delete the redis cache pod, and create a new one, the error is still there.

[17:21:29 ERR] An unhandled exception has occurred while executing the request. Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name 'IsDeleted'. Invalid column name 'CreationTime'. Invalid column name 'CreatorId'. Invalid column name 'DeleterId'. Invalid column name 'DeletionTime'. Invalid column name 'IsDeleted'. Invalid column name 'LastModificationTime'. Invalid column name 'LastModifierId'. at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__195_0(Task1 result) at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location --- at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SplitQueryingEnumerable1.AsyncEnumerator.InitializeReaderAsync(AsyncEnumerator enumerator, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func4 operation, Func4 verifySucceeded, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.Internal.SplitQueryingEnumerable1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToListAsync[TSource](IQueryable1 source, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToListAsync[TSource](IQueryable1 source, CancellationToken cancellationToken) at Volo.Abp.OpenIddict.Authorizations.EfCoreOpenIddictAuthorizationRepository.FindAsync(String subject, Guid client, String status, String type, CancellationToken cancellationToken)

I noticed ABP has these code:

context.Services .AddDataProtection() .SetApplicationName("MyApp") .PersistKeysToStackExchangeRedis(redis, "MyApp-Protection-Keys");

However, if our application want to use Microsoft Data Protection API to encyrpt/decrypt business data, we have this settings: services.AddDataProtection() .ProtectKeysWithAzureKeyVault(new Uri(keyId), new DefaultAzureCredential(new DefaultAzureCredentialOptions { ManagedIdentityClientId = keyVaultClientId })) .PersistKeysToAzureBlobStorage(azureStorageConnectionString, containerName, EncrptionConsts.DataProtectionKeyBlobName) .SetDefaultKeyLifetime(TimeSpan.FromDays(36500));

Would these two settings conflict with each other, can we simply comment out ABP's AddDataProtectioncode?

Thanks

The Angular app stand alone set to true

in app.component.ts file

import { RoutesService, ConfigStateService, ReplaceableComponentsService, eLayoutType, ABP, BaseCoreModule } from '@abp/ng.core';
...
private readonly routes = inject(RoutesService);

OnInit(): void {
this.routes.add([
  {
        path: 'dashboard',
        name: ComponentNames.ES_DASHBOARD,
        iconClass: 'fas fa-chart-line',
        order: 5,
        layout: eLayoutType.application,
        requiredPolicy: Permissions.DASHBOARD_MONITORING_DASHBOARD,
      } as ABP.Route,
]);
}

Above code add additional menu item to left-side menus, however, sometimes, the added menu items are not shown.

When upgrade to Abp 9.1.1, we still keep existing .Net projects instead of single project for each Micro Service. I noticed there are IdentityServiceDynamicPermissionDefinitionsChangedEventHandler.cs and IdentityServiceChangeIdentityPasswordPolicySettingDefinitionProvider.cs which doesn't exist in codebase in ABP 8.

If we keep existing ABP 8 solution layout, do we need to add above files somewhere?

Update ABP Studio to latest version From menu change ABP version 9.1.2, create a new solution (Micro Service) After create the solution, check each .Net project, the ABP package version is 9.1.1

Microservice Template.

In localhost:4200, the console app has this error:

The source code is in this method: function setModuleVisibilityFactory(stream, service, identifier) { return stream.pipe(map(features => features.enable), tap(enable => { const { children, ...tree } = service.find(r => r.name === identifier); tree.invisible = !enable; service.patch(identifier, tree); })); }

After upgrade and deployed the site to QA env,

For the same tenant, some users login, they got this exception in ABP log: /api/account/my-profile [ { "code": "Volo.Authorization:010001", "message": "Authorization failed! Given policy has not granted.", "details": null, "data": null, "validationErrors": null } ]

When we test the ABP 9.1.1 upgrade code, when login via MFA (Phone), sometimes we get 409 error, but nobody else using the same account to login

After upgrade to ABP 9, the component scroll bar is gone. From console log, ERROR TypeError: Cannot read properties of null (reading 'scroll') at DashboardSummaryComponent.scrollToTop

ABP 9.1.1

For String Encryption implemented by ABP https://abp.io/docs/latest/framework/infrastructure/string-encryption Is there a size limitation to for the data to encrypt/decrpt?