nens / servicedesk-issue-only

This repository will be used primarily by the service desk to report issues which will then be moved by the teamleads
0 stars 0 forks source link

[3Di]: user not redirected to login - trouble with logging in and out (staging only) #139

Open GeOdin opened 1 year ago

GeOdin commented 1 year ago

Contact Details

No response

Topdesk URL (API)

No response

Incident Type

Error

What priority should we assign to this submission?

Prio2 Urgent

3Di component

Livesite

What happened?

When I started the staging live site https://www.staging.3di.live/, I had trouble logging in. The screen stayed on 'Waiting for authentication'

After logging in via the api, I could login in the staging live site. https://api.staging.3di.live/v3/auth/profile/

But when I tried to log out via staging live, something similar occured.

How to Reproduce?

Go to the staging live site https://www.staging.3di.live/ You will have trouble logging in. The screen will stay on 'Waiting for authentication'

Go to https://api.staging.3di.live/v3/auth/profile/ and login there.

Go back to staging live https://www.staging.3di.live/ You may need to refresh the page (CNTRL + SHFT + R), but you'll be logged in

Log out from staging https://www.staging.3di.live/ The same issues occurs

What did you expect and what was the actual result?

I did not expect that logging in and out would cause the screen to stay on the 'Waiting for authentication screen.

Add screenshots, video's etc

Chrome Error

20231027 - 3di staging - laadt niet 2 chome

Firefox

Response header

20230127 - 3di staging laadt niet 4   firefox

Request header

20230127 - 3di staging laadt niet 5   firefox

Relevant log output

Failed to load resource: the server responded with a status of 401 ()
main.186080ba36db1054.js:2 User is not redirected to login, but this might be a mistake. Check file session.ts line 87 t/m 97
Navigated to https://www.staging.3di.live/
main.186080ba36db1054.js:2          GET https://api.staging.3di.live/v3/auth/profile/ 401
fetchApi @ main.186080ba36db1054.js:2
request @ main.186080ba36db1054.js:2
await in request (async)
authProfileListRaw @ main.186080ba36db1054.js:2
authProfileList @ main.186080ba36db1054.js:2
(anonymous) @ main.186080ba36db1054.js:2
(anonymous) @ main.186080ba36db1054.js:2
n.<computed> @ main.186080ba36db1054.js:2
(anonymous) @ main.186080ba36db1054.js:2
il @ main.186080ba36db1054.js:2
wu @ main.186080ba36db1054.js:2
(anonymous) @ main.186080ba36db1054.js:2
w @ main.186080ba36db1054.js:2
P @ main.186080ba36db1054.js:2
I.<computed> @ polyfills.02c0442975564d2f.js:1
T @ polyfills.02c0442975564d2f.js:1
j @ polyfills.02c0442975564d2f.js:1
main.186080ba36db1054.js:2 User is not redirected to login, but this might be a mistake. Check file session.ts line 87 t/m 97

Additional info

Did something change about the authentication?

Good luck! :)

GeOdin commented 1 year ago

Note: similar response in Chrome, FireFox and Edge.