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

OIDC token refresh failing #8420

Closed
wkloucek opened this issue Feb 13, 2023 · 1 comment · Fixed by #8762
Closed

OIDC token refresh failing #8420

wkloucek opened this issue Feb 13, 2023 · 1 comment · Fixed by #8762
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working

Comments

@wkloucek
Copy link
Contributor

Steps to reproduce

  1. Log in to https://ocis.ocis-web.daily.owncloud.works/
  2. Wait some minutes
  3. See screen that you have been logged out. If you click on "login again" you will be immediately logged in again

If you watch the browser console you will see this:

image

Expected behaviour

Token refresh works and indeed it does on https://ocis.ocis-traefik.daily.owncloud.works

Actual behaviour

The "logged out" screen appears

Environment general

Latest oCIS master with latest web

@wkloucek wkloucek added the Type:Bug Something isn't working label Feb 13, 2023
@tbsbdr tbsbdr added the Priority:p2-high Escalation, on top of current planning, release blocker label Feb 13, 2023
@tbsbdr
Copy link
Contributor

tbsbdr commented Feb 13, 2023

Console Screenshot in higher resolution:
Clipboard - February 13, 2023 12_36 PM

A » [IFrameWindow] navigate: no state found in response url
• • (oidcClient] readSigninResponseState: Error: No state in response at Pfe. readSigninResponseState (vendor-aceee24.mjs:2:96800)
at Pfe.processSigninResponse (vendor-aceee24.mis:2:97145)
at fo. signinEnd (vendor-ac6eee24.mjs:2:117839)
at fo. signin (vendor-ac6eee24.mjs:2:117349)
at async fo.signinSilent (VM242 vendor-aceee24.mjs:2:114818)
at async Ufe. tokenExpiring (VM242 vendor-aceee24.mjs:2:111289)
© > (SilentRenewService] tokenExpiring: Error from signinSilent: Error: No state in response
at Pfe. readSigninResponseState (vendor-aceee24.mis:2:96800)
at Pfe.processSigninResponse (vendor-aceee24.mis:2:97145)
at fo. signinEnd (vendor-ac6eee24.mjs:2:117839)
at fo. signin (vendor-ac6eee24.mjs:2:117349)
at async fo.signinSilent (VM242 vendor-ac6eee24.mjs:2:114818)
at async Ufe. tokenExpiring (VM242 vendor-aceee24.mjs:2:111289)
© Silent Renew Error: Error: No state in response
at Pfe. readSigninResponseState (vendor -aceee24.mjs:2:96800) at pfe.processSigninResponse (vendor-ac6eee24.mis:2:97145)
at fo. signinEnd (vendor-aceee24.mis:2:117839)
at fo. signin (vendor-aceee24.mis:2:117349)
at async fo.signinSilent (VM242 vendor-aceee24.mis:2:114818)
at async Ufe. tokenExpiring (VM242 vendor-aceee24.mjs:2:111289)
[UserManagerl removeUser: user removed from storage user unloaded...
[UserManagerl getUser: user not found in storage
© • Uncaught TypeError: Cannot read properties of null (reading 'style')
at Proxy. onResize (web-app-search-6c65a554.mis:1:5016)
A An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants