-
Notifications
You must be signed in to change notification settings - Fork 159
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
Authentication logic is fragile #7030
Labels
Milestone
Comments
kulmann
added
Type:Bug
Something isn't working
Priority:p1-urgent
Consider a hotfix release with only that fix
labels
May 23, 2022
One symptom / massive annoyance of the broken token refresh in ocis: #7008 |
The maintainer of |
9 tasks
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We currently have multiple issues in the way the web ui handles authentication.
Touchpoints:
Tasks:
oidc-client
=> we decided to use
oidc-client-ts
as a replacement as it seems to be much more active in development and is in good shapeauthService
, state in store should only contain the userinfo and capabilities, not the auth logicoidc-client-js
withoidc-client-ts
ready
hook of all applicationsuserLoaded
event from theoidc-client-(j|t)s
lib is only fired once after login, otherwise the event is suppressed. idea 1: implement own storage provider to intercept the event. idea 2: make an upstream contribution to get an event. 3: find out if we can know through other indications if the user is (already) loaded.userReady
hookset oidc-client-ts logging level through configThe text was updated successfully, but these errors were encountered: