hi
You can feedback it on https://github.com/abpframework/abp/issues/new
hi
Add MyMultiTenantConnectionStringResolver to your CMVPoint.IdentityService.MongoDB project, I will fix this in 5.3 patch version.
using System;
using System.Threading.Tasks;
using Microsoft.Extensions.Options;
using Volo.Abp.Data;
using Volo.Abp.DependencyInjection;
using Volo.Abp.MultiTenancy;
namespace CMVPoint.IdentityService.MongoDb;
[Dependency(ReplaceServices = true)]
public class MyMultiTenantConnectionStringResolver : MultiTenantConnectionStringResolver
{
public MyMultiTenantConnectionStringResolver(
IOptionsMonitor<AbpDbConnectionOptions> options,
ICurrentTenant currentTenant,
IServiceProvider serviceProvider)
: base(options, currentTenant, serviceProvider)
{
}
public override Task<string> ResolveAsync(string connectionStringName = null)
{
if (connectionStringName == "Volo.Abp.Identity.MongoDB.IdentityProMongoDbContext")
{
return base.ResolveAsync("AbpIdentity");
}
return base.ResolveAsync(connectionStringName);
}
public override string Resolve(string connectionStringName = null)
{
if (connectionStringName == "Volo.Abp.Identity.MongoDB.IdentityProMongoDbContext")
{
return base.Resolve("AbpIdentity");
}
return base.Resolve(connectionStringName);
}
}
hi
Can you share the source code with me? liming.ma@volosoft.com
HI
We will discuss, Thanks.
hi
What are the migration steps for LDAP in 5.3.x Is LDAP Integration here to stay in future ABP versions?
The LDAP feature moved to the Identity module after 5.3, It's just that the namespace has changed a bit. It is still available. https://docs.abp.io/en/commercial/latest/modules/identity/ldap
If you get issues you can share your code and logs.
Any plans to keep the IDS support option? Any plans for Commercial IDS support?
I will ask the team about this.
hi
You can debug the YourProjectNameTenantDatabaseMigrationHandler service, and make sure it will be called when a tenant is created.
hi
It seems that the connection string is not getting correctly.
You can debug the connectionStringResolver try to get the connection string.
var connectionStringResolver = ServiceProvider.GetRequiredService<IConnectionStringResolver>();
hi
We will check this.
hi
You just need to replace the default mailing service, it's that simple.