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
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
And then /easyauth/signout-callback-oidc endpoint suppose to remove AzAD.EasyAuthForK8s http-only cookie. And since it's not happening the workaround will be to have our own endpoint which will do that for us (which is still not optimal, since the session is not invalidated)
The text was updated successfully, but these errors were encountered:
You are correct that the sign out is not currently implemented. We wanted to provide some options around the behavior (federated vs cookie only, how this would work with bearer tokens, etc.), but didn't have time in the last iteration. If you can provide some details around how you would want it to behave in your use case, we can take it under consideration.
Thanks for the answer! I assume that there should be a way to invalidate tokens/cookies and remove cached information about the user. An endpoint triggering cookie invalidation+removal for the user themselves will be enough for us at this point.
I also assume it to be core functionality, since currently it's not possible to use EasyAuthForK8s-based auth on a public equipment and in general sounds scary to have no way to invalidate sessions in case of leaks / phishing / user deletion / etc.
Or is there any other implemented way to clear internal user cache?
Am I understanding correctly, that there is no sign out functionality implemented, since
signedOutCallbackPath
is marked asReserved for future use - Not currently used
?Currently, my understanding is that we need to construct sign out url ourselves, like so:
And then
/easyauth/signout-callback-oidc
endpoint suppose to removeAzAD.EasyAuthForK8s
http-only cookie. And since it's not happening the workaround will be to have our own endpoint which will do that for us (which is still not optimal, since the session is not invalidated)The text was updated successfully, but these errors were encountered: