Activities of "gterdem"

Thank you, I suggest switching to static proxying since dynamic proxying will make your gateways depend on microservices.

But if you want to use dynamic proxying with the ocelot, you can also do so.

Sine the generated templated using dynamic proxy, can we use dynamic Client Proxies?

For microservice template, if you change static proxy to dynamic proxy; gateways will need to depend on Http.Api layers of the dynamic proxying microservices which is not a subtle way to handle.

Which generated template is using dynamic proxy? Newly created microservice? Can you share the command you used to create the microservice?

This is not related to ABP. As I mentioned above, to sign out from external identityserver; you need to implement front-channel or back-channel logout mechanism to the external identityserver.

Try abp install-libs command under the project you are getting this error.

They are false errors. IDE showing javascript-related errors, especially related to node_modules, can be ignored and you should also ignore them.

You need to run dotnet build /graphBuild under main solution to restore your solution. Also please check Microservice getting started documentation.

Logout page of external IdentityServer which will announce clients to sign out.

Can you share your AuthServer.csproj package references?

Can you share the exact logs after running abp new <solution name> -t microservice-pro -u mvc?

The nodejs log above doesn't seem right with ABP microservice creation.

Thank you,

We should put Account related changes migration guide if it is missing.

Please let me know asap once you put all changes related to account module in migration guide as my Application is about to ready for production and I recently upgraded abp version to 5.2.0 due to this issue https://support.abp.io/QA/Questions/2809/httpssupportabpioQAQuestions2558Identity-Server-Error---Microservices

Thank you in advance.

You may have misunderstood that, there are no changes on the Account Module.
The Account Module was hosted by Http.Api.Host application of a tiered (separate identityserver) solution. It has been moved to IdentityServer project. That's all.

Okay. So, I will not be able to access through web gateway by adding it into configuration? I have to access those api through Identity server endpoint?

My WebGateway appsettings configuration.

No, you are right. In the microservice template; gateways should be updated. account endpoints should be redirected to AuthServer instead of IdentityService. I have taken note of adding this to the migration guide.