问题
Does anyone have experience with running IdentityServer4 in a web farm (multiple IIS servers) behind a load balancer? We've had some issues getting 2 servers to work together. I didn't see a deployment guide for IdentityServer4. There is one here for IdentityServer3.
https://identityserver.github.io/Documentation/docsv2/advanced/deployment.html
We have implemented the DataProtection in the Startup.cs.
StackExchange.Redis.ConnectionMultiplexer connectionMultiplexer = RedisConnectionFactory.GetConnection();
RedisKey redisKey = appSettings.RedisKeyPrefix;
services.AddDataProtection().PersistKeysToRedis(connectionMultiplexer, redisKey);
The load balancer is running in layer 7. It decrypts the SSL and re-encrypts so it can inspect and update the headers with the X-Forwarded-For value. We added the ForwardedHeadersOptions in the Startup.cs for this so the application sees the IP of the end-user and not the load balancer.
services.Configure<ForwardedHeadersOptions>(options =>
{
options.ForwardedHeaders =
ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto;
options.KnownNetworks.Add(new IPNetwork(...);
options.KnownProxies.Add(...);
});
Our configuration and operational stores both use SQL.
Am I missing something to ensure 2 servers in a farm can work together? Should we expect that both cookie and token validation should process correctly when inspecting the cookies and tokens initially generated by the other server in the farm?
来源：https://stackoverflow.com/questions/52174647/tips-for-running-identityserver4-in-a-web-farm