You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you extend a kratos session using the admin API,
the next call to the public toSession()/Whoami REST API will then return a new cookie.
This new cookie must be returned to the UI and used for future UI requests;
I believe the cookie contains an expiry data as part of its encrypted payload.
This is not explained in the kratos documentation and if this is not done,
UI requests start to fail when the original session expires even though the
session in the database has been updated.
Reproducing the bug
Not really relevant
Relevant log output
not relevant
Relevant configuration
not relevant
Version
kratos 1.1.0
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker Compose
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Ory Network Project
No response
Describe the bug
If you extend a kratos session using the admin API,
the next call to the public toSession()/Whoami REST API will then return a new cookie.
This new cookie must be returned to the UI and used for future UI requests;
I believe the cookie contains an expiry data as part of its encrypted payload.
This is not explained in the kratos documentation and if this is not done,
UI requests start to fail when the original session expires even though the
session in the database has been updated.
Reproducing the bug
Not really relevant
Relevant log output
Relevant configuration
not relevant
Version
kratos 1.1.0
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker Compose
Additional Context
No response
The text was updated successfully, but these errors were encountered: