I operate an IIS-hosted application and need to consolidate all incoming client requests so they appear as one user to the backend. What configuration or strategy can achieve this?
try using a reverse proxy with a token based auth, it tend to be more robust than relying on sticky sessions. it can reassign headers and combine client reqs under one identity.
Based on my experience with IIS, consolidating client requests into a single identity can be achieved by employing a custom middleware that inspects requests and injects a unified token before reaching the backend. This method worked well when combined with IIS URL Rewrite to adjust the headers appropriately. The key is to ensure that the token validation remains robust and seamlessly integrated with your authentication framework. This approach allowed for centralized identity management without affecting the performance of the overall system.
hey, im curious if anyone tried arr with sticky sessions for this? i think that may merge client requests on iis. anyone else got experince or additional tips? lets discuss!