identityserver-hosting-setup

To host IdentityServer in ASP.NET Core, you must configure DI registration using AddIdentityServer and set up the middleware pipeline with UseIdentityServer in the correct order. This ensures secure middleware sequencing and proper service registration for production deployments.

Proper middleware ordering places UseIdentityServer at the correct position in the ASP.NET Core pipeline to ensure secure sequencing. Correct DI registration via AddIdentityServer is also required before the middleware can handle authentication requests safely.

You integrate ASP.NET Identity with Duende IdentityServer by calling AddAspNetIdentity during DI registration. This configures the shared hosting pattern to manage user authentication alongside IdentityServer's protocol handling seamlessly.

IdentityServer supports both separate and shared hosting patterns. A separate project isolates security concerns, while a shared application uses AddAspNetIdentity to combine IdentityServer with your existing ASP.NET Core user interface and APIs.

Configuring forward headers and data protection is required for secure IdentityServer deployments. This setup ensures correct client IP resolution and consistent authentication ticket handling across multiple application instances.

License key management is part of configuring Duende IdentityServer during the DI registration phase. You must apply the license key correctly to satisfy production deployment requirements and remove the developer license warning.