Activities of "gterdem"

galip.erdem@volosoft.com a zoom davetiyesi gönderir misiniz? TR saati ile 17:00’den sonra mümkünse.

error: When I authorize a method in A service I get error 403 because admin user can't have permissions of A service

Putting aside how you write the permissions to AdministrationService, is the problem related to admin user is granted by default with the seeded(?) new permissions?

How do you seed the permissions of Service A? Is it auto-migration (seeding DataSeedContributor on OnPostApplicationInitialization)? DbMigrator?

Permission'ların AdministrationService'e nasıl yazıldığını bir kenara bırakırsak, admin kullanıcısının default olarak neden yeni yazılan permission'lara sahip olmadığını mı soruyorsunuz tam olarak?

Service A permission'ları nasıl yazıyorsunuz? OnPostApplicationInitialization method'unda DataSeedContributor'ı mı çalıştırıyorsunuz (auto-migration)? DbMigrator mı kullanıyorsunuz?

It can not find the implementation of IDataSeedingRoleAppService because it is under the application layer.

I couldn't understand why did you create an application service for data migration. You can create dataseed contributors and instead of an application service, you can create a DataSeeder (implementing IDataSeeder) and seed it.

See https://docs.abp.io/en/abp/latest/Data-Seeding#idataseeder for more information.

You can use any tool to generate self-signed certificate or use any CA signed certificate.

dotnet dev-certs https -v -ep authserver.pfx -p YOURPASSWORD is a way to generate it. YOURPASSWORD must match with the AuthServerModule code where it reads this file.

You are using wildcard ('*') with .AllowCredentials. You need to whitelist the origins.

You can configure CORS in publicwebdev app as:

context.Services.AddCors(options =>
{
    options.AddDefaultPolicy(builder =>
    {
        builder
            .WithOrigins("https://eventstreamingapidev.azurewebsites.net")
            .WithAbpExposedHeaders()
            .SetIsOriginAllowedToAllowWildcardSubdomains()
            .AllowAnyHeader()
            .AllowAnyMethod()
            .AllowCredentials();
    });
});

Hello,

Yes, gateways in microservice template locates the re-routing services and add them as swagger definitions. Currently, we are trying to find a way to cover this scenario better, where microservices do not expose any swagger ui but the gateway exposes the swagger ui with all the endpoints it re-routes to.

However the solution will most likely differ based on the gateway library.

Currently, you can alter the gateway swagger ui manually.

You can try to use a midware to redirect the incoming traffic to https. Something like:

app.Use((httpContext, next) =>
{
    httpContext.Request.Scheme = "https";
    return next();
});

It maybe misconfiguration of endpoints aswell. The same are already configured by default, you can also try removing all the configuration after SetIssuer.

Can you share browser console logs and AdministrationService logs?

Unprotected ticket failed doesn't seem to be related to this.

Remove

remoteEnv: {
    url: '/getEnvConfig',
    mergeStrategy: 'deepmerge'
  }

from environment.prod.ts file and re-publish please.

For your second application, you can check the public-web application that whichever references you need. For resolving the tenant, you need to have the UseMultiTenancy midware and the related dependency with connection string to Saas Service.

Another confusion is releted to default product Microservice that are autogenerated on solution. Why, in angular app, the microservice is "connected" directly to productMicroservice and not to the gateway?

It is redirecting to webgateway, localhost:44325 is the web gateway address.