Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Websocket liveness check #108

Open
NHAS opened this issue May 8, 2024 · 0 comments
Open

Websocket liveness check #108

NHAS opened this issue May 8, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@NHAS
Copy link
Owner

NHAS commented May 8, 2024

Currently the moment wag detects a change to the incoming source IP/port of a client they are deauthenticated, and forced to relog in.

This can be frustrating on high churn networks such as mobile networks or folk behind cgnats.

If on the login page we issued a session token that could prove that the client device was still safe, we could omit the deauthenticated and challenge cycle leading to better user experience.

This will most likely be something in 8.1
0

@NHAS NHAS added the enhancement New feature or request label May 8, 2024
@NHAS NHAS self-assigned this May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant