Refresh when 401 received from API or WebSocket for improved UX when running behind a reverse proxy that handles authentication #252

New Issue

2026-10-05T02:06:03+02:00

adam commented

2026-10-05 02:06:03 +02:00

💡 What would you like to see?

As a user I would like the web front end to refresh or have the ability to redirect to a specified URL when it receives an HTTP 401 or HTTP 403 from the API
So that I can reauthenticate with my reverse proxy
So that I can continue to use RemoteTerm

🤔 What problem does it solve?

RemoteTerm provides basic HTTP authentication to keep the API layer secure. Basic authentication causes issues with modern browsers and password managers, often requiring reauthentication on a frequent basis, especially when using the web front end on a mobile device. Password managers often do not handle basic authentication in an elegant way, making it hard for the user to reauthenticate.

One way to improve the situation is to put RemoteTerm behind a reverse proxy such as nginx proxy manager and use an IdP such as authelia to handle authentication.

However, when the authelia session expires, the RemoteTerm front end does not handle this situation very well. Either the user has to refresh the page, triggering a redirect to authelia, or if the user is running the front end as a PWA then the user has to force quit the app.

Putting in place an automatic refresh or a way to redirect to a specific URL would allow the user to easily reauthenticate with the IdP.

📋 Additional context

RemoteTerm 3.17.1

## 💡 What would you like to see? As a user I would like the web front end to refresh or have the ability to redirect to a specified URL when it receives an HTTP 401 or HTTP 403 from the API So that I can reauthenticate with my reverse proxy So that I can continue to use RemoteTerm ## 🤔 What problem does it solve? RemoteTerm provides basic HTTP authentication to keep the API layer secure. Basic authentication causes issues with modern browsers and password managers, often requiring reauthentication on a frequent basis, especially when using the web front end on a mobile device. Password managers often do not handle basic authentication in an elegant way, making it hard for the user to reauthenticate. One way to improve the situation is to put RemoteTerm behind a reverse proxy such as nginx proxy manager and use an IdP such as authelia to handle authentication. However, when the authelia session expires, the RemoteTerm front end does not handle this situation very well. Either the user has to refresh the page, triggering a redirect to authelia, or if the user is running the front end as a PWA then the user has to force quit the app. Putting in place an automatic refresh or a way to redirect to a specific URL would allow the user to easily reauthenticate with the IdP. ## 📋 Additional context - RemoteTerm 3.17.1

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#252