Internet Information Services (IIS) as Reverse Proxy for SITMUN #19
Description
Is your feature request related to a problem? Please describe.
Many existing SITMUN 2 deployments rely on IIS for public exposure. Therefore, SITMUN 3 must be similarly accessible through IIS to maintain consistency and meet organizational requirements. Without clear guidance, teams may struggle to configure IIS as a reverse proxy for SITMUN 3’s front-end and back-end services.
Describe the solution you'd like
A comprehensive guide that details how to configure IIS as a reverse proxy for SITMUN 3. This should include URL Rewrite and ARR (Application Request Routing) configuration for forwarding traffic to the SITMUN containers or deployed artifacts.
Describe alternatives you've considered
- Using other web servers or load balancers (e.g., Nginx, Apache) instead of IIS, which can introduce new infrastructure requirements.
- Exposing SITMUN 3 directly on its own port or domain, bypassing IIS entirely—unsuitable for organizations that rely on a standardized IIS environment.
Additional context
Many government or institutional setups require IIS to remain the primary public interface. Offering clear, step-by-step documentation for configuring SITMUN 3 behind IIS will speed up adoption, reduce deployment friction, and allow SITMUN 3 to integrate seamlessly with existing infrastructure.