Skip to content

Commit 0d1a06e

Browse files
Merge pull request #9511 from mendix/kv-broken-links
Session Management: broken links
2 parents 35c648f + 57d3ab5 commit 0d1a06e

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

content/en/docs/refguide/runtime/session-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ If you do not want your offline-first app to create an authentication token, you
6161

6262
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.
6363

64-
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.
64+
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.
6565

6666
### Client-Runtime Session Management Flow
6767

content/en/docs/refguide10/runtime/session-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Below Mendix version 10.9.0, there is no support for authentication tokens.
7474

7575
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`.
7676

77-
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.
77+
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.
7878

7979
### Client-Runtime Session Management Flow
8080

0 commit comments

Comments
 (0)