as per understanding GetAsync method of AbpApplicationConfigurationAppService will be useful for adding or modifying the Application Configuration Endpoint right? do u think this this Method will be called for all service calls from the application?
Yes, you should override the GetAsync method to modify the Application Configuration Endpoint (if your version is lower than v6.0). This endpoint calls by some framework services. (provides localization key-values, permissions etc.)
Thanks for the response @engincan, but I think there is some miss understanding. we are looking to add additional info (custom headers and adding additional query parameter for the request URI) for all of the API calls. but AbpApplicationConfigurationAppService only talks about configuration API right....?
Thanks for the response, but it looks like this will work in 6.0 only as of now ours is 5.1.3 , do u have any alternate for this or do we need to upgrade to 6.0?
If you do not want to upgrade your project, you can override the
GetAsync
method of AbpApplicationConfigurationAppService in your project and update it to your needs.
as per understanding GetAsync method of AbpApplicationConfigurationAppService will be useful for adding or modifying the Application Configuration Endpoint right? do u think this this Method will be called for all service calls from the application?
Hi @viswajwalith ,
That's fine, at least can you point the code/file where we had to inject some additional logic before the call of any API call happening from the application.
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.AspNetCore.Mvc/Volo/Abp/AspNetCore/Mvc/ApplicationConfigurations/AbpApplicationConfigurationAppService.cs#L85-L122
You can add some additional properties to this endpoint without overriding the AbpApplicationConfigurationAppService, you can read this article to see how to extend this endpoint and get a general knowledge about this endpoint.
Thanks for the response, but it looks like this will work in 6.0 only as of now ours is 5.1.3 , do u have any alternate for this or do we need to upgrade to 6.0?
hi
This is an endpoint that the framework has to call, you can't prevent it.
That's fine, at least can you point the code/file where we had to inject some additional logic before the call of any API call happening from the application.
We have tried HttpContextIdentityModelRemoteServiceHttpClientAuthenticator but not all API calls are coming under this unless we included the webgateway. Please advise if we missed anything.
hi
It works for the framework. You don;t need to call it.
But when the application is starting up, it it being called internally can you guide us in preventing the calling of those (MVC UI)
We had to pass additional query string parameter along with ReturnUrl to the Auth Server (when the application is redirecting from Application to Auth Server on the initial call) , Can you guide us the relevant file/code to achieve the same.
When we are running our MVC application of our Micro Service based solution, we have been observed that api/abp/api-defination and api/abp/api-configuration being called, any specific usage for this? if possible we don't want to have that called if no use.
Please advise.
Hi
Steps to reproduce the issue
-installed Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX package to existing project (5.1.3 version ) -Deleted <PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton" Version="5.1.3" /> reference in web Proj file -Deleted "using Volo.Abp.LeptonTheme.Management;" references from web module class files. -added this to web module class file "using Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX;" -added "typeof(AbpAspNetCoreMvcUiLeptonXThemeModule)" in class file -removed all references related to old lepton theme like Bundling, Components and below reference @using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Themes.Lepton.Components.Content.Alerts @using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Themes.Lepton.Components.Content.BreadCrumb @using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Themes.Lepton.Components.Content.Title @using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Themes.Lepton.Components.Header @using Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton.Bundling
Basically we need to connect to SQL MI with managed identity, so thought of modifying the connection method to accommodate the same, but .Net 6 is having native support for the same so updating to Sql.Data.Client to 5.1 fulfilled our requirement.
Thanks for the support, I am closing the issue from my side.
We are trying to update to LeptonX from Lepton Theme, added all the necessary packages but still getting the below error ? any guidance to fix this out?