Read encrypted session data again on reopen#34934
Conversation
|
Possible performance regression detected Show Output |
nickvergessen
left a comment
There was a problem hiding this comment.
Good find.
- Together with nextcloud/spreed#8265 that finally solves nextcloud/spreed#4670
|
This actually seems to break the login |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Possible performance regression detected Show Output |
|
Does this potentially fix #33919? |
4b9a565 to
8de8a01
Compare
|
Does this fix #33919? Edit: seems like not |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
…e removed Signed-off-by: Julius Härtl <jus@bitgrid.net>
8de8a01 to
c412821
Compare
|
Tests are passing again, rebased and squashed |
Yes, doesn't seem related to that. |
|
/backport to stable25 |
|
Failure unrelated, fix is in #34954 |
|
Confirmed, reverting the two commits makes cypress pass again. |
|
@skjnldsv Can you reproduce that outside of cypress as well? There it seems to work for me. Will try to run the viewer cypress tests and see if I can reproduce that |
|
I can reproduce but only when running the cypress test. Seems somehow the |
|
A few debugging insights:
I'll need to think a bit about what the best approach there would be. Session data after login with a different user{
"LAST_ACTIVITY": 1667572677,
"requesttoken": "wOirYlodceLJwwObK2nqX\\/LMGiGSoBsh",
"checkServer_succeeded": true,
"login_credentials": {
"run": true,
"uid": "rzeketu1",
"loginName": "rzeketu1",
"password": "password",
"isTokenLogin": false
},
"AUTHENTICATED_TO_DAV_BACKEND": "admin",
"last-password-confirm": 1667572674,
"user_id": "rzeketu1",
"loginname": "rzeketu1",
"timezone": "1",
"token_scope": {
"filesystem": true
}
}Full list of session write calls for a cypress run |

This should avoid working with outdated session data after reopening the PHP session