From 57d3ab5972fbb1d69d860d39d915283a7acbbd47 Mon Sep 17 00:00:00 2001 From: Karuna-Mendix Date: Fri, 9 May 2025 14:48:09 +0530 Subject: [PATCH] Fixed broken links --- content/en/docs/refguide/runtime/session-management.md | 2 +- content/en/docs/refguide10/runtime/session-management.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide/runtime/session-management.md b/content/en/docs/refguide/runtime/session-management.md index ef052e16d8d..d93639a38d7 100644 --- a/content/en/docs/refguide/runtime/session-management.md +++ b/content/en/docs/refguide/runtime/session-management.md @@ -61,7 +61,7 @@ If you do not want your offline-first app to create an authentication token, you By default, authentication tokens will not be used in online Mendix apps. However, you can use them to remember the end-user. For more information see [Working with Authentication Tokens](#work-with), above. -Online apps still utilize the [EnableKeepAlive](/refguide/tricky-custom-runtime-settings/#session-duration) setting to maintain uncommitted data which changes during the session. If that setting is disabled and `useAuthToken` is set to `true`, uncommitted changes will be lost if an action is performed after the session expires, which occurs after the [SessionTimeout](https://github.com/refguide/custom-settings/#SessionTimeout). In this case, the authentication token is used to reinitialize the session to keep user signed in, after which the application is reloaded. +Online apps still utilize the [EnableKeepAlive](/refguide/tricky-custom-runtime-settings/#session-duration) setting to maintain uncommitted data which changes during the session. If that setting is disabled and `useAuthToken` is set to `true`, uncommitted changes will be lost if an action is performed after the session expires, which occurs after the [SessionTimeout](/refguide/custom-settings/#SessionTimeout). In this case, the authentication token is used to reinitialize the session to keep user signed in, after which the application is reloaded. ### Client-Runtime Session Management Flow diff --git a/content/en/docs/refguide10/runtime/session-management.md b/content/en/docs/refguide10/runtime/session-management.md index 9f74c25f5d7..d2da52a8992 100644 --- a/content/en/docs/refguide10/runtime/session-management.md +++ b/content/en/docs/refguide10/runtime/session-management.md @@ -74,7 +74,7 @@ Below Mendix version 10.9.0, there is no support for authentication tokens. By default, authentication tokens will not be used in online Mendix apps version 10.9.0 and above. However, you can use them to remember the end-user by writing your own flow using the new API, `login2`, and setting the `useAuthToken` parameter to `true`. -Online apps still utilize the [EnableKeepAlive](/refguide10/tricky-custom-runtime-settings/#session-duration) setting to maintain uncommitted data which changes during the session. If that setting is disabled, in Mendix apps version 10.9.0 and above where `useAuthToken` is set to `true`, uncommitted changes will be lost if an action is performed after the session expires, which occurs after the [SessionTimeout](https://github.com/refguide10/custom-settings/#SessionTimeout). In this case, the authentication token is used to reinitialize the session to keep user signed in, after which the application is reloaded. +Online apps still utilize the [EnableKeepAlive](/refguide10/tricky-custom-runtime-settings/#session-duration) setting to maintain uncommitted data which changes during the session. If that setting is disabled, in Mendix apps version 10.9.0 and above where `useAuthToken` is set to `true`, uncommitted changes will be lost if an action is performed after the session expires, which occurs after the [SessionTimeout](/refguide10/custom-settings/#SessionTimeout). In this case, the authentication token is used to reinitialize the session to keep user signed in, after which the application is reloaded. ### Client-Runtime Session Management Flow