I have answered at https://support.abp.io/QA/Questions/3310#answer-084e1ddb-1b93-8b19-d5be-3a04c64322e3
Can you check if your new microservice registers the Cors configuration using the cors middleware?
In NewServiceHttpApiHostModuleat ConfigureServices method should contain below:
context.Services.AddCors(options =>
{
options.AddDefaultPolicy(builder =>
{
builder
.WithOrigins(
configuration["App:CorsOrigins"]
.Split(",", StringSplitOptions.RemoveEmptyEntries)
.Select(o => o.Trim().RemovePostFix("/"))
.ToArray()
)
.WithAbpExposedHeaders()
.SetIsOriginAllowedToAllowWildcardSubdomains()
.AllowAnyHeader()
.AllowAnyMethod()
.AllowCredentials();
});
In NewServiceHttpApiHostModule at OnApplicationInitialization method should contain:
...
app.UseRouting();
app.UseCors(); // Check for this
app.UseAuthentication();
...
Now you can add api-gateway url to appsettings so that NewMicroservice can allow for any header with any method to the origins specified at appsettings.
From the localization files at Domain.Shared layer. Each module defines its own localization with a Localization resource. You can check Localization docs for more information.
On top of localization, we have the Language Management module which is pre-installed in Administration Service. You can check Language Management docs for more information.
Also, both the https://www.mycompany.net and https://app.mycompany.net redirect the login to http://auth.mycompany.net not https which gives a 404.
Setting auto-redirect in webserver from HTTP to HTTPS should fix this problem.
Browsing to https://auth.mycompany.net I still get The cookie 'XSRF-TOKEN' has set 'SameSite=None' and must also set 'Secure'.
What is this application? Angular back-office application or mvc application?
Can you check the logs?
Also you can override the SignInManager and debug then see what's going on.
Possible cross-origin (CORS) issue? The URL origin (https://localhost:44472) does not match the page (https://localhost:44325). Check the server returns the correct 'Access-Control-Allow-*' headers.
What is running on port 44325? Your new microservice? You need to add https://localhost:44472 to your new microservice appsettings Cors configuration.
Your document doesn't seem to be updated to 5.3.. There is no internal gateway, and the other gateways do not rely anymore on a project reference for the HttpApi Projects. I did update ocelot.json, the specific Module.cs, but still get the error.
We have updated the documentation but maybe we forgot some of it. Can you point which documentation have internal gateway reference?
Your document "Change Microservice project to use MongoDB Provider" changes everything to mongo. But i would only add one additional service with mongo. There is a difference , that both Migrations and Checker must work at same time.. and the document doesn't describe that clearly. I did look at eshoponabp and it a looks a bit different.
It has actually commented code to activate MongoDB for a single microservice. You can also check the eShopOnAbp sample that CatalogService is using MongoDB.
If you are using Kubernetes, yes.
You need to check the IdentityService values to override.
You can check the IdentityServerDataSeeder file. It is located under both the DbMigrator and the IdentityService.HttpApi.Host projects
Whichever you are using to seed the data, check the appsettings.json file for IdentityServer initial data. You can examine the IdentityServerDataSeeder to learn where they are used and set.
This seems to be related to the dotnet tye project. Can you raise an issue with your setting in tye repository?
I know that a pro template is not a microservice. But i want to move the relevant parts from pro template solution to a new microservice .. Thats why asked for a guide.. I think its a valid option for moving towards a microservice solution
What do you mean by relevant parts? You can move the domain layer to the domain, the application layer to the application layer. It shouldn't be any problem.
The only exception with the microservice is the UI. Because there are 2 ways to build the UI;
Can you provide some samples of the issue you are having?