Activities of "gterdem"

If you are going to use it for names only, data duplication makes more sense imho.

But if you want to keep users in your microservice to use for different scenarios as well, you can create a lookup user like ProductUser to keep in your microservice. Check the CmsUser for implementation details.

Then you can create an IProductUserLookupService to handle user lookups. See ICmsUserLookupService and CmsUserLookupService for implementation details.

This service checks if the local user exists, if it doesn't exist, it makes an external request to IdentityService and saves it as the local user and returns the user. You can also override the default behavior and configure it to check the external source all the time. See UserLookup implementation for more details.

1. To make the ExternalUserLookupServiceProvider for the microservice, you need to configure your microservice as a client. In the IdentityServer/OpenIddict DataSeeder, add your microservice as a client (like the administration service). You can check the CmsService in eShopOnAbp registered to use IdentityService as a client with the required UserLookup permission. 2. Add

<PackageReference Include="Volo.Abp.Identity.HttpApi.Client" Version="your-prefered-version" />
<PackageReference Include="Volo.Abp.Http.Client.IdentityModel.Web" Version="your-prefered-version" />

project references to the microservice that contains the UserLookUp service and don't forget to add

typeof(AbpIdentityHttpApiClientModule),
typeof(AbpHttpClientIdentityModelWebModule)

to the microservice API host module. 3. Add configuration for server-to-server communication in the appsettings.json with the client_id you have set in the identityserver/openIddict data seeder as in the CmsService client credentials configuration sample.

Now you can inject IProductUserLookupService and search/find users.

The heath-check mechanism for microservices is handled by DevOps mainly; Kubernetes, docker-compose, etc.

You need to add it manually if you are not using orchestration.

Try abp logout then abp login again.

AddMicrosoftIdentityWebApp is basically using the OpenIdConnect. Try getting token manually and calling the Graph API as in the sample above since we don't have direct support for Microsoft Graph API.

Can you share the Fluent API configuration under onModelCreating for the Phase entity?

public class Project : AuditedAggregateRoot<Guid>, IMultiTenant
{
    public Guid? TenantId { get; protected set; }
    public string Name { get; protected set; }
    public string Description { get; protected set; }
    public Guid BaseModelId { get; protected set; }
}

public class Phase : AuditedAggregateRoot<Guid>, IMultiTenant
{
    public Guid? TenantId { get; protected set; }
    public Guid ProjectId { get; protected set; }
    public string Name { get; protected set; }
    public string Description { get; protected set; }
}

Only added DbSets and no fluent API configuration: Although, you don't need to implement IHasExtraProperties for the AggregateRoot since it already implements it.

CreatorId should be audited anyway so you can use the ExternalUserLookupService to get detailed info about the user.

Although, you can also duplicate the data. You can add the CreatorName (or what else I need) to the Product entity.

Sorry, I don't have knowledge about self-signed certificates on IIS or the IIS itself. There should be guides about it on the web.

Considering the OpenSSL and the mkcert, you should be passing the domain names for the SSL but I don't know about the IIS.

Basically, there are 2 ways to for UI development in a microservice template: - Modular UI development: Add the UI pages in the microservice itself by referencing the HttpApi.Client and Web layers by the end application. We use this sample in the eShopOnAbp back-office application (angular) - Monolith UI development: Develop the UI inside the end-running application by referencing the HttpApi.Client layer. We use this sample in the eShopOnAbp public-web application (mvc/razor).

More info at microservice UI development docs.

But I assume you are not asking this exactly. If I understand correctly, you ask for a way of providing report-like data for the UI that combines data from multiple microservices. (Correct me if I am wrong)

In that case, you can use the gateway aggregator pattern to achieve that. There are some gateways that can already handle this (even with UI like KrakenD). The microservice template uses ocelot and ocelot has also request aggregation that you can use. Although, the gateways are running applications. You can manually write your aggregator or manual code to call for different microservices and return for a manual request.

We don't have an example for that yet and it is not automatically supported since we use proxying directly based on the end-points. You need to write custom end-points for both the application and the request handler (gateway).

But we plan to handle this scenario in the eShopOnAbp sample once we decided how to do it.

Try abp logout and abp login again in the CLI.

Can you share the cert creation code? If it is the dotnet dev certs command, it will only generate for localhost and won't work in the production.

You can use tools like cmake, openssl for generating self-signed certificates or use Lets Encrypt. dotnet dev certs is for localhost only and not for production.