​

nonsense

I’ve had a big deployment problem lately. Keep a record

The company’s small project, IdentityServer4+API+Blazor, took a few days to work on and is finally ready for deployment

Intermediate deployment process omitted ten thousand words…

Record various issues:

[IDS4] IdentityServer4, known/ openID-configuration: HTTPS required

NetCore project Blazor is deployed to the IIS server. Many modules need to be downloaded and installed

[Windows] Cannot start this program because apI-ms-win-crt-runtime-L1-1-0.dll is missing in the computer

IdentityServer4 deployed to IIS

.

The text start

After a messy deployment process, download various runtime environments, various modules

Failed to load resource: net::ERR_CONNECTION_REFUSED

During a visit to http://localhost:5601/.well-known/openid-configuration at fault

​

The deployed port setup looks like this

5601 is part of the IdentityServer4 project, named XXX.IDS

5602 belongs to the API project, named XXX.API

5603 is the Blazor project, named xxx.web, for convenience

Analysis of the

In the process of solving the problem, I also asked various technical groups, and later I learned that there may be a configuration problem

The various urls and ports are configured in the project through the configuration file appsetting.config

[root@localhost] [root@localhost] [root@localhost] [root@localhost] [root@localhost] [root@localhost

Later, I tried to change the address to the IP address of the server, and all three items were changed

​

The url needs to be configured in each project

The IDS project needs to configure the deployment URL of the Web project for authorization

The API project needs to configure the deployment URL of the IDS project, that is, the authorization address

The web project needs to configure the deployment URL of ids project and API project for authorization and access to API resources

To solve

After a while of torture, I finally can

​

Authorization was successful.

After this problem, I finally realized that the configuration file is still divided into two files

​

Two configuration files,

One is the configuration of the development environment

Another is the configuration of the deployment environment

Write the configuration URL of the development environment to localhost

The IP address of the deployment environment is the actual IP address

Also, internal servers do not deploy HTTPS

HTTPS deployment requires certificate issuance, which is a bit troublesome and failed after a long time

Use direct deployed HTTP for the Intranet

Complete the WC…

​