Activities of "ademaygun"

Hi Engin Can, Yes, I found the foreign key error, there is no problem at the moment. We need to get used to the new test framework structure, we would love for you to explain in detail why such a change was made with a blog post or a live broadcast. Because we are trying very hard to write test codes. For example, finding the foreign key error can be very difficult. Finally, when the entity is created, the EfCore[Entity]DomainTests class is not created, I had to create this class myself. I would be happy if an issue record is opened for this. Thank you for your support.

Hi Engin Can, I had to create EfCoreAbcDomainTests class for my Entity. Abp Studio should automatically generate this class for each entity. When I run it I get the following error. I get the same error for SampleDomainTest:

---- Microsoft.EntityFrameworkCore.DbUpdateException : An error occurred while saving the entity changes. See the inner exception for details.
-------- Microsoft.Data.Sqlite.SqliteException : SQLite Error 19: 'FOREIGN KEY constraint failed'.

Hi, I made the following changes but I still get another error

• protected -> public
• public abstract class SampleDomainTests : AbcDomainTestBase where TStartupModule : IAbpModule -> public class SampleDomainTests : AbcDomainTestBase<AbcDomainTestModule> But this time I get this error:

---- Autofac.Core.DependencyResolutionException : An exception was thrown while activating Volo.Abp.PermissionManagement.PermissionDataSeedContributor -> Volo.Abp.Authorization.Permissions.PermissionDefinitionManager -> Volo.Abp.PermissionManagement.DynamicPermissionDefinitionStore.
-------- Autofac.Core.DependencyResolutionException : None of the constructors found on type 'Volo.Abp.PermissionManagement.DynamicPermissionDefinitionStore' can be invoked with the available services and parameters:
Cannot resolve parameter 'Volo.Abp.PermissionManagement.IPermissionGroupDefinitionRecordRepository permissionGroupRepository' of constructor 'Void .ctor(Volo.Abp.PermissionManagement.IPermissionGroupDefinitionRecordRepository, Volo.Abp.PermissionManagement.IPermissionDefinitionRecordRepository, Volo.Abp.PermissionManagement.IPermissionDefinitionSerializer, Volo.Abp.PermissionManagement.IDynamicPermissionDefinitionStoreInMemoryCache, Microsoft.Extensions.Caching.Distributed.IDistributedCache, Microsoft.Extensions.Options.IOptions`1[Volo.Abp.Caching.AbpDistributedCacheOptions], Microsoft.Extensions.Options.IOptions`1[Volo.Abp.PermissionManagement.PermissionManagementOptions], Volo.Abp.DistributedLocking.IAbpDistributedLock)'.```

Hello Sumeyye, I apologize for my incorrect expression. Can you please try the same test by entering this address: https://localhost:44326/account/login instead of http://localhost:4200. (Do not start the Angular project)

Hello, But In MVC login(authorization code), if "remember me" is not active, when we close and open the browser, it asks us to log in again.

Hi Sumeyye, I don't understand what you mean. The "remember me" feature should work as @Sinan997 mentioned, but I don't think it does. Have you tried creating a new project?

Hi, Just checking if there's any update on my issue. Thanks

I know that the cookie needs to be deleted, I actually deleted it but it seems to remain, anyway the problem is solved

Hi, I found the solution; I set the 'Front Channel Logout URI' value to https://account.abc.com/account/logout, and my problem was resolved. However, if I upgrade my abp project to v.6+, it seems that you don't have such a solution in your OpenID Connect configuration

Hi, We have two separate projects on the same codebase. The first project needs to work with local login, while the second one needs to use external provider. Therefore, we need two identity servers. Currently, when we log out from the Angular UI (authorization code flow), it logouts from our project, but not from the external provider.