-
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 Pop-up appears because /notifications/sse request uses expired bearer token #9635
Comments
@lookacat could you take over ? |
But isn't this also an oCIS bug? Even if the token is expired, I wouldnt expect the header to require a password to be sent |
Turns out web was missing the proper |
Ah, yes, that's probably what I was thinking of, not the Authorization header |
looks like that #9654 did not solve the pop-up problem |
@ScharfViktor It looks like the |
Hmm I'm not able to reproduce it on my system. Can you send me your ocis config flags? Also, are you running ocis locally or via our Docker dev setup? |
re-tested on |
ocis 4.0.0
web 7.1.0-rc.5
Steps:
Expected result: no authentication Pop-up
Actual result: after token refreshing appears the authentication Pop-up
because request https://host.docker.internal:9200/ocs/v2.php/apps/notifications/api/v1/notifications/sse uses expired bearer token
The text was updated successfully, but these errors were encountered: