You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe the problem.
I would like to be able to host Aspire Dashboard behind a reverse proxy such as NGINX. Unfortunately, Aspire Dashboard doesn't take X-Forwarded-* headers into consideration, and doesn't allow to configure a path base.
The issue of the path base has already been described in #4528 and #4159. Additionally, authentication through OpenID Connect fails to set the correct value for redirect_uri, as it uses the internal schema (HTTP) rather than the external one (HTTPS).
davidfowl
changed the title
Dashboard: add support for a reverse proxy or load balancer
Make it possible to run the dashboard behind a reverse proxy or load balancer
Sep 16, 2024
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
I would like to be able to host Aspire Dashboard behind a reverse proxy such as NGINX. Unfortunately, Aspire Dashboard doesn't take
X-Forwarded-*
headers into consideration, and doesn't allow to configure a path base.As an example, assume Aspire Dashboard is accessible internally from http://aspire-dashboard-service:18888/ and externally from https://example.com/dev/aspire-dashboard/ through a reverse proxy.
The issue of the path base has already been described in #4528 and #4159. Additionally, authentication through OpenID Connect fails to set the correct value for
redirect_uri
, as it uses the internal schema (HTTP) rather than the external one (HTTPS).Describe the solution you'd like
It's possible to add support for reverse proxies and load balancers as described here:
https://learn.microsoft.com/aspnet/core/host-and-deploy/proxy-load-balancer
Ideally, all the featured described in previous page (except for certificate forwarding) should be configurable by the user, namely:
X-Forwarded-*
headers)Additional context
No response
The text was updated successfully, but these errors were encountered: