eclipse-opendut
Token refresh resets unsaved data
When authentication is enabled in LEA (e.g. in the Testenv), an access token refresh happens every 5 minutes. If this happens while the user is editing a peer or cluster without their changes yet, this resets their entered data to the last saved state. If they never saved, the data is cleared entirely.
This is caused by the token refresh triggering a re-render, which causes LEA to fetch the PeerDescriptor for the given ID from the backend. Then it fills in the fetched values without regard for the user edits.
As a side-note, the next version of leptos-oidc will likely fix a problem, so that instead of these frequent access token refreshes, only the refresh token is refreshed e.g. once per hour. This would make these UI resets much less common, but would still happen occasionally, if users leave the UI open for a while.
