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
The issue you're experiencing with the authentication token not refreshing and causing unexpected logouts could be related to the token refresh mechanism in Dify. The current implementation involves verifying the refresh token, generating new tokens, and updating them in the Redis store [1]. However, there might be specific conditions or configurations in Dify Cloud that are affecting this process, such as session timeout settings or token expiration intervals, which are not detailed in the available information.
To address this issue, you might want to check the following:
Token Expiration and Refresh Intervals: Ensure that the token expiration and refresh intervals are configured correctly in your Dify Cloud setup. Unfortunately, specific default settings for these intervals are not available in the provided information.
Session Timeout Configuration: Verify if there is a session timeout or inactivity timeout configured that might be causing the session to end prematurely.
Logging and Monitoring: Check if there are any logs or monitoring tools available that could provide insights into why the token refresh is failing or why the session is expiring unexpectedly.
If these checks do not resolve the issue, it might be necessary to look into the Dify Cloud configuration or reach out to the maintainers for further assistance.
Self Checks
Dify version
0.14.1
Cloud or Self Hosted
Cloud
Steps to reproduce
✔️ Expected Behavior
Auth token refreshes as long as there is user activity. Possibly up to a maximum of a few days before re-logging in is forced
❌ Actual Behavior
The text was updated successfully, but these errors were encountered: