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

WebSocker-Next - Refresh OIDC AccessToken without reconnection #43434

Open
dometec opened this issue Sep 22, 2024 · 2 comments
Open

WebSocker-Next - Refresh OIDC AccessToken without reconnection #43434

dometec opened this issue Sep 22, 2024 · 2 comments

Comments

@dometec
Copy link

dometec commented Sep 22, 2024

Description

At the moment, when an access token expires, the WebSocker-Next server closes the connection.
Sometimes, it's a problem since a token life span can be very short (a few minutes) and reconnection can be expensive.
Is it possible to think of some mechanism that allows the client to refresh the token before it expires and not close the websocket connection?

Implementation ideas

Maybe a PATCH request to the same WebSocket endpoint to update the access token can be a solution?

@dometec dometec added the kind/enhancement New feature or request label Sep 22, 2024
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 22, 2024

/cc @pedroigor (oidc), @sberyozkin (oidc)

@sberyozkin
Copy link
Member

The tricky part is to have an expired but earlier verified token replaced with a token which has also been verified by Quarkus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants