By default, IdentityServer requires SSL (for obvious reasons). But there are scenarios where IdentityServer might be deployed behind a load balancer or proxy server. In those situations it might be desirable to relax the SSL requirement in IdentityServer. I’m pleased to announce that this is now supported (with some configuration). You can read the details of the configuration from the docs.
Enjoy.
leastprivilege.com 
Hi! This is good to read!
My current urgent concern is related to load balancers and high availability solutions. Apart from removing SSL, would anything else be needed to let the IdentityServer run with several instances (behind a load balancer for instance) without creating any issues when we have multiple client requests (such as concurrency issues, race conditions, sessionfulness, …)? Reading the doc, it appears to me everything comes out of the box, however I just want to make sure I am not missing anything.
Thanks a lot for an answer,
Maximilian
A shared config database of course. But besides that you should be fine.
Thanks a lot for the fast reply. I’ll let you know via this blog, if I ran into more problems ;)