[jmvvliet] said: Thanks! Would add a lot of value and is complementary to the BookStore example (BookTypes) provided by ABP :)
I agree, it's a great feature that fits well with the BookStore example and how BookTypes are used. It will definitely add value. Thanks again for the suggestion!
Hi, thanks for the feature request! We've created an internal issue to track it and will include it in our planning.
Best regards.
Hi, ABP does not check if the URL is empty or not, it's a nullable field, because in your code you may want to write audit logs for any internal process call. For example, you may want to audit log your event handlers and for these cases, the URL should be emptyl and you can also think similar scenerios where HttpContext is not in the place.
If you don't want to log if the URL is empty, then you can create audit log contributor or configure AbpAuditingOptions and add a selector to its AlwaysLogSelectors property. (See https://abp.io/docs/latest/framework/infrastructure/audit-logging#abpauditingoptions)
Can we use LocalEventBus as a replacement for DistributedEventBus, particularly for intra-service communication in modules like Identity and SaaS, assuming they are hosted within the same process or closely coupled?
Hi, for distributed systems (and microservices), it's suggested to use distributed events, because of the inter-service communication without tight coupling services to each other. If you don't have a requirement for that, then you can use the local event bus, but most of the time, it will probably not be feasible for development and you will require distributed events. (Unless, you want to tightly couple your services, and this breaks the microservices architecture, because you will not be able to independently deploy your services and so on..)
Is it possible to dynamically switch between LocalEventBus and DistributedEventBus based on a configuration setting (e.g., from appsettings.json) so the same codebase can support both environments (with or without distributed messaging)?
Unfortunately, there is no feature flag for that. But, if you use IDistributedEventBus by default, and switch its provider as LocalDistributedEventBus for a custom setting/option, then it will work like a local event bus. (By default, if you don't configure a provider it uses LocalDistributedEventBus by default and it works as a local event bus - in memory -)
[dshapiro] said: For authentication we should define a new OpenID application within ABP and configure Elsa Studio to authenticate via OIDC? Or perhaps there's a simpler way to accomplish this as Elsa Server is hosted within the ABP project, so should have direct access to the Identity provider.
Hi, for authenticating Elsa Studio with your ABP based application, the recommended approach (as you stated) is to define a new OpenID Connect (OIDC) application within your ABP AuthServer. Then, configure Elsa Studio to authenticate against your ABP AuthServer using this new OIDC client.
Elsa might be providing a sample for integrating with a .NET application with identity, maybe you can check it through its repository or elsa-samples repository.
Regards.
[g.hasan@tatweermea.com] said: Sure, email sent
Thanks. We will check the report and get back to you.
Regards.
Hi, for LeptonX Theme customization, you can refer to the following links:
Hi, we have documentation for that: https://abp.io/docs/commercial/6.0/modules/identity/ldap
Can you please check it? We provide a UI for that, so you can easily configure ldap settings and using it in your ABP based application.
Regards.
[DuHK] said: I deleted the above configuration but when I run it again, I still get this error. Give me an example so that when a user changes their password the first time they log in, the token is returned.
Your module need to depend on AbpIdentityAspNetCoreModule or you should add the following configuration:
public override void PreConfigureServices(ServiceConfigurationContext context)
{
PreConfigure<IdentityBuilder>(builder =>
{
builder.AddDefaultTokenProviders()
});
}
See https://github.com/abpframework/abp/issues/9009#issuecomment-841082012 for more information.