Activities of "uyarbtrlp"

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello, We want to change "entityTypeFullName" property on entity changes in audit logging module. I assume that it is retrieved from the namespace. We don't want to change the namespace for that. How we are going to change this value while adding the record?

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Tiered (for MVC): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

Hello all, We want to send an email confirmation token from Angular app and we want to use MVC keyword(AuthServer confirmation page) for that (not separate Angular UI). Before that, I've wanted to try it on HttpApi.Host. We've added Volo.Abp.Account.Pro.Public.HttpApi dependency in HttpApi module. I am able to see the endpoints on swagger UI After that, when we call the send-email-confirmation-token from the HttpApi.Host, I see that there is empty url in the email. To achieve that problem, I've added the AbpUrlOptions to HttpApi.Host module to set the RoorUrl for "MVC" keyword and give the AuthServer url since email confirmation page is here. Swagger authority is set as AuthServer url. When I try it on my local, everything works fine but it does not work for the docker containers. I get the error invalid token even though the link is correct.

How can I solve that problem?

Is using the client credentials flow suggested if I want to use the remote service in the background job?

• ABP Framework version: v7.3.1
• UI Type: MVC
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..)
• Module Template (Separated Deployment & Databases Scenario): yes

Hello,

As I've mentioned here , I call the file management app service, which is implemented on AuthService as if it is a microservice, on my domain service by using remote service call. I use static proxy scripts to achieve that. When I call it, I get an authorization error since we don't have httpContext access on background job. I implement AbpHttpClientIdentityModelWebModule on HttpApi.Host to pass the current token to authorization header (not using the AbpHttpClientIdentityModelModule with client_credentials flow)

Here is the part of my domain service method (ExportAsBaseModelAsync) which uses fileDescriptorAppService:

Here is the background job:

Here is the error log on HttpApi.Host and AuthServer

How can I send the request behalf of the user with current token? Is there a way to do that magically like ApplicationService methods?

Hello again,

When I run the command abp generate-proxy -t csharp -u http://localhost:53929/ -m fileManagement in domain layer, I can see that files generated But the project gives compile error since there are missing packages regarding application service. For example:

I guess adding the Volo.Abp.Application.Services package is not a right way to do it. How to resolve that?

Okay. Thanks for suggestions

Okay, I got it. Besides its functionality, we don't want to generate the proxy scripts when every time code changes. When I examine here, we think that X ABP module is an external API and Y module shouldn't work without X module service (at least on some business logics). We know that there is a dependency issue. Let's say that I have a business logic that should run with X module API and I need to call it in domain service. I think Y.Domain like a client application and we can reference HttpApi.Client layer on Y.Domain layer since we run a business logic by using X module API.

Do we violate the rules in terms of DDD by giving the X.HttpApi.Client reference to Y.Domain or is it a basically dependency issue that we should think about?

If I understand it correctly, I need to add X.HttpApi.Client reference to Y.Domain. If the answer is yes, I have two questions:

• Is it best practice to consume X module API on domain layer by referencing X.HttpApi.Client?
• If it is not the best practice, should we call remote service on application layer by referencing X.Application.Contracts to Y.Application.Contracts?

Hello,

I have a X module and I want to call one of its API on Y module in domain service. I want to use Synchronous Communication. Since the interface is in X.Application.Contracts and give the reference on Y.Application.Contracts, I am not able to use it in domain service. What is the best practice to call ABP module API in domain service?

Thanks

• ABP Framework version: v5.3.3
• UI type: MVC
• DB provider: EF Core
• Tiered (MVC): yes

Hello all,

We've been trying to make our OSS clearing. Our OSS clearing team have found @transloadit/prettier-bytes package which has a confusing license issue and said that it could be risky to use it for customers since it has AGPL license. When I look into the package-lock.json file of xx.IdentityServer project, I can see that it comes from @volo/account not directly but it's subcomponents.

When I examine the source code of the package, I see that the main source code has AGPL-v3 license. But when I go the packages folder and find the prettier-bytes folder, it is written as MIT license. https://github.com/transloadit/monolib/tree/%40transloadit/prettier-bytes%400.0.7. Also, when I search it on npm, I can confirm that it has MIT license for this version. Our team thinks that AGPL license overwrites MIT since the main source code has AGPL license. I know it is a strange case but I want to know your opinion or approach. We don't want to open our repository to public, of course. Is it safe to use it for end customers? What do you think about this issue?