Hi,
Yes, it's a problem, we are working on it. it should be fixed soon.
Hi,
We will check it.
they are configuring multiple databases in one module
The database is separated, and each module can have its own database, by configuring the connection string, a module can access the b database
See: https://docs.abp.io/en/abp/latest/Connection-Strings
Or you can use the C# API client proxies, This way you can access the API, but not directly read the database in the module
And as we Can See if I am Adding the Date Of Birth in Configure Extra property It's Showing DD-MM-YY-HH-MM-AM I need only DD-MM-YYYY can anyone suggest how to configure that....
You can add DisplayFormatAttribute to the extra property:
ObjectExtensionManager.Instance.Modules()
.ConfigureIdentity(identity =>
{
identity.ConfigureUser(user =>
{
user.AddOrUpdateProperty<DateTime>(
"Birthday",
property =>
{
var format = new DisplayFormatAttribute()
{
DataFormatString = "dd/MM/yyyy"
};
property.Attributes.Add(format);
}
);
});
});
Hi,
You can set the connection string. See: https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Migrations#change-the-connection-strings-section
Hi,
I think your main problem has been solved and the new problem is not related to this.
Could you create a new question? thanks.
Hi,
Unfortunately, the access token is immutable by design and re-login is required.
But you can add a new Middleware to dynamically update the current claims. For example: https://support.abp.io/QA/Questions/2090/How-to-clear-cache-for-features#answer-f36c97e0-8c78-c2ca-8362-3a000f923d93
Hi,
Yes, it's possible.
Just an idea:
You can create a new page to allow the tenant to register their own application.
Here are the TokenController methods you need to override:
ClientCredentials
You need to add TenantId to the AccessToken: https://github.com/abpframework/abp/blob/dev/modules/openiddict/src/Volo.Abp.OpenIddict.AspNetCore/Volo/Abp/OpenIddict/Controllers/TokenController.ClientCredentials.cs#L34
Application name should be unique even for different tenants.
Hi,
You can custom the UserStore to override the CreateAsync method to enable the two-factor by default.
For example:
[ExposeServices(typeof(IdentityUserStore))]
public class MyIdentityUserStore : IdentityUserStore
{
public MyIdentityUserStore(IIdentityUserRepository userRepository, IIdentityRoleRepository roleRepository, IGuidGenerator guidGenerator, ILogger<IdentityRoleStore> logger, ILookupNormalizer lookupNormalizer, IdentityErrorDescriber describer = null) : base(userRepository, roleRepository, guidGenerator, logger, lookupNormalizer, describer)
{
}
public override async Task<IdentityResult> CreateAsync(IdentityUser user, CancellationToken cancellationToken = new CancellationToken())
{
await SetTwoFactorEnabledAsync(user, true, cancellationToken);
return await base.CreateAsync(user, cancellationToken);
}
}
PS: User must confirm his email and mobile number to use two-factor
Hi,
Unfortunately, it's hard to do because it requires you to customize the ABP source code.
reason why we don't want to upgrade to latest version is we still using identity server if we upgrade to latest version we are forcing to change many things in current project.
Hi, you will not miss something. we still release the IdentityServer package.you can keep using it
Hi,
Are you using the IdentityServer or OpenIddict as a auth server? because from 6.0.0 the app template uses OpenIddict by default.