Ok, Waiting for good news.
hi lalitChougule
I don't recommend you to do this. But you can try to use Dapper to read the database directly.
hi
I think you can change the tenant, but change the user is currently impossible.
using (CurrentTenant.Change(tenantId))
{
long userCount = await _userLookupService.GetCountAsync();
}
hi
Although it took me a long time to run your application, it is not easy to execute. I need to delete a lot of environment information that I don’t have, But I think I found the problem. Your application uses the wrong migration.
The SCV.Litmus.IdentityServer
has own migrations file. but the migrations in SCV.Litmus.EntityFrameworkCore.DbMigrations
project is the right migration that app will use.
Everything is works when I connectiong to the database generated by SCV.Litmus.EntityFrameworkCore.DbMigrations
in the SCV.Litmus.IdentityServer
.
So please try to understand and check your migrations.
hi
I received your project, Checking.
Message=Unable to resolve service for type 'Volo.Abp.Identity.IIdentityUserRepository' while attempting to activate 'Volo.Abp.Identity.IdentityUserStore'.
The IdentityUserStore
service implementation is in the EF Core module.
HI
The link is the alper shared. But you said you can't access it.
https://support.aspnetzero.com/QA/Questions/9809/How-do-I-implement-logout-all-client-with-Identity-Server-4#answer-7d351498-32de-92e6-a92b-39f8bf30a871
Hello @trungbttsd,
I think implementing front-channel logout will solve your problem. However it is a bit complicated and tricky at first glance.
You need to update your identityServer clients with the following:
You need to add a new page to redirect after logging out, to signout from other clients and/or redirect back to your client. You can see sample implementations of our LoggedOut.cshtml and LoggedOut.cshtml.cs.
I hope this will be helpful.
hi
I think it need those project.
<ProjectReference Include="..\..\shared\SCV.Litmus.Shared\SCV.Litmus.Shared.csproj" />
<ProjectReference Include="..\..\shared\SCV.Litmus.Utils\SCV.Litmus.Utils.csproj" />
Can you try build at your local before send to avoid other build problem? Thanks
hi
<PackageReference Include="Volo.Saas.EntityFrameworkCore" Version="4.3.0" />
using Volo.Saas.EntityFrameworkCore;
typeof(SaasEntityFrameworkCoreModule)
Acme.MyConsoleApp>dotnet run
[15:25:20 INF] Starting console host.
[15:25:21 INF] Loaded ABP modules:
[15:25:21 INF] - Acme.MyConsoleApp.MyConsoleAppModule
[15:25:21 INF] - Volo.Abp.Autofac.AbpAutofacModule
[15:25:21 INF] - Volo.Abp.Castle.AbpCastleCoreModule
[15:25:21 INF] - Volo.Saas.Host.SaasHostApplicationModule
[15:25:21 INF] - Volo.Saas.SaasDomainModule
[15:25:21 INF] - Volo.Abp.MultiTenancy.AbpMultiTenancyModule
[15:25:21 INF] - Volo.Abp.Data.AbpDataModule
[15:25:21 INF] - Volo.Abp.ObjectExtending.AbpObjectExtendingModule
[15:25:21 INF] - Volo.Abp.Localization.AbpLocalizationAbstractionsModule
[15:25:21 INF] - Volo.Abp.Validation.AbpValidationAbstractionsModule
[15:25:21 INF] - Volo.Abp.Uow.AbpUnitOfWorkModule
[15:25:21 INF] - Volo.Abp.EventBus.Abstractions.AbpEventBusAbstractionsModule
[15:25:21 INF] - Volo.Abp.Security.AbpSecurityModule
[15:25:21 INF] - Volo.Saas.SaasDomainSharedModule
[15:25:21 INF] - Volo.Abp.Localization.AbpLocalizationModule
[15:25:21 INF] - Volo.Abp.VirtualFileSystem.AbpVirtualFileSystemModule
[15:25:21 INF] - Volo.Abp.Settings.AbpSettingsModule
[15:25:21 INF] - Volo.Abp.FeatureManagement.AbpFeatureManagementDomainSharedModule
[15:25:21 INF] - Volo.Abp.Validation.AbpValidationModule
[15:25:21 INF] - Volo.Abp.Domain.AbpDddDomainModule
[15:25:21 INF] - Volo.Abp.Auditing.AbpAuditingModule
[15:25:21 INF] - Volo.Abp.Json.AbpJsonModule
[15:25:21 INF] - Volo.Abp.Timing.AbpTimingModule
[15:25:21 INF] - Volo.Abp.Threading.AbpThreadingModule
[15:25:21 INF] - Volo.Abp.EventBus.AbpEventBusModule
[15:25:21 INF] - Volo.Abp.Guids.AbpGuidsModule
[15:25:21 INF] - Volo.Abp.ObjectMapping.AbpObjectMappingModule
[15:25:21 INF] - Volo.Abp.ExceptionHandling.AbpExceptionHandlingModule
[15:25:21 INF] - Volo.Abp.Specifications.AbpSpecificationsModule
[15:25:21 INF] - Volo.Abp.AutoMapper.AbpAutoMapperModule
[15:25:21 INF] - Volo.Abp.FeatureManagement.AbpFeatureManagementDomainModule
[15:25:21 INF] - Volo.Abp.Features.AbpFeaturesModule
[15:25:21 INF] - Volo.Abp.Authorization.AbpAuthorizationAbstractionsModule
[15:25:21 INF] - Volo.Abp.Caching.AbpCachingModule
[15:25:21 INF] - Volo.Abp.Serialization.AbpSerializationModule
[15:25:21 INF] - Volo.Saas.Host.SaasHostApplicationContractsModule
[15:25:21 INF]
Hello World!
] - Volo.Abp.Application.AbpDddApplicationModule
[15:25:21 INF] - Volo.Abp.Application.AbpDddApplicationContractsModule
[15:25:21 INF] - Volo.Abp.Authorization.AbpAuthorizationModule
[15:25:21 INF] - Volo.Abp.Http.AbpHttpAbstractionsModule
[15:25:21 INF] - Volo.Abp.GlobalFeatures.AbpGlobalFeaturesModule
[15:25:21 INF] - Volo.Abp.FeatureManagement.AbpFeatureManagementApplicationContractsModule
[15:25:21 INF] - Volo.Abp.FeatureManagement.AbpFeatureManagementApplicationModule
[15:25:21 INF] - Volo.Saas.EntityFrameworkCore.SaasEntityFrameworkCoreModule
[15:25:21 INF] - Volo.Abp.EntityFrameworkCore.AbpEntityFrameworkCoreModule
[15:25:21 INF] - Volo.Abp.FeatureManagement.EntityFrameworkCore.AbpFeatureManagementEntityFrameworkCoreModule
[15:25:21 INF] Initialized all ABP modules.
[15:25:21 INF] Application started. Press Ctrl+C to shut down.
[15:25:21 INF] Hosting environment: Production
[15:25:21 INF] Content root path: Acme.MyConsoleApp
HI
It depends on where your dynamic permissions are stored. If your application is a monolithic application, you can consider try to inject the repository.
In short, don't call application services, because this will cause an infinite loop.