From d461ca157652ab76abbd018572c1977d018c79ba Mon Sep 17 00:00:00 2001 From: Albert ten Napel Date: Tue, 17 Nov 2026 10:53:18 +0100 Subject: [PATCH] Document that inactive users lose their sessions Since RUN-5428 the runtime ends sessions of inactive users, but blocking a user still leaves their existing sessions alive. --- .../modeling/security/app-security/user-roles.md | 2 +- content/en/docs/refguide/runtime/login-behavior.md | 12 ++++++++++++ content/en/docs/refguide10/runtime/login-behavior.md | 12 ++++++++++++ content/en/docs/refguide9/runtime/login-behavior.md | 12 ++++++++++++ 4 files changed, 37 insertions(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/security/app-security/user-roles.md b/content/en/docs/refguide/modeling/security/app-security/user-roles.md index 9711b1a6628..bfac90e7805 100644 --- a/content/en/docs/refguide/modeling/security/app-security/user-roles.md +++ b/content/en/docs/refguide/modeling/security/app-security/user-roles.md @@ -93,7 +93,7 @@ Users who can manage an end-user can make the following changes: * UserRoles – Grant or remove the selected user roles, but only those user roles which are selected under **User management** * Name * User_TimeZone -* Blocked +* Blocked – see [Blocked and Inactive Users and Existing Sessions](/refguide/login-behavior/#blocked-and-inactive-users-and-existing-sessions) * Active * User_Language diff --git a/content/en/docs/refguide/runtime/login-behavior.md b/content/en/docs/refguide/runtime/login-behavior.md index b33862ac01d..e268bf105e2 100644 --- a/content/en/docs/refguide/runtime/login-behavior.md +++ b/content/en/docs/refguide/runtime/login-behavior.md @@ -18,6 +18,18 @@ The cluster manager does more than just unblocking users. For example, it also r Cluster manager behavior currently cannot be changed. {{% /alert %}} +## Blocked and Inactive Users and Existing Sessions + +Blocking a user, either automatically after failed login attempts or manually by setting the **Blocked** attribute of the user, only prevents that user from signing in again. It does not end sessions the user already has. This is deliberate: otherwise anyone could sign another user out by entering a wrong password for their account three times. + +Setting the **Active** attribute of a user to false does end their existing sessions. The session is ended on the user's next request, on every node of the cluster. + +If you block a user manually because they should lose access immediately, also set them to inactive or delete their sessions (`System.Session` objects associated with the user). + +{{% alert color="info" %}} +Ending the sessions of inactive users was introduced in Mendix 11.17.0, 11.12.9, and 11.6.14. In earlier versions, an inactive user could keep using an existing session for as long as it was kept alive. +{{% /alert %}} + ## Customizing Login Behavior Login behavior can be customized by implementing a custom Java action and registering it to be used instead of the default login action. To do this you need to perform the following steps, saving the updated Java in the `javasource` folder of your app. diff --git a/content/en/docs/refguide10/runtime/login-behavior.md b/content/en/docs/refguide10/runtime/login-behavior.md index 9a24d5a54f6..e9156c5e8fc 100644 --- a/content/en/docs/refguide10/runtime/login-behavior.md +++ b/content/en/docs/refguide10/runtime/login-behavior.md @@ -18,6 +18,18 @@ The cluster manager does more than just unblocking users. For example, it also r Cluster manager behavior currently cannot be changed. {{% /alert %}} +## Blocked and Inactive Users and Existing Sessions + +Blocking a user, either automatically after failed login attempts or manually by setting the **Blocked** attribute of the user, only prevents that user from signing in again. It does not end sessions the user already has. This is deliberate: otherwise anyone could sign another user out by entering a wrong password for their account three times. + +Setting the **Active** attribute of a user to false does end their existing sessions. The session is ended on the user's next request, on every node of the cluster. + +If you block a user manually because they should lose access immediately, also set them to inactive or delete their sessions (`System.Session` objects associated with the user). + +{{% alert color="info" %}} +Ending the sessions of inactive users was introduced in Mendix 10.24.30. In earlier versions, an inactive user could keep using an existing session for as long as it was kept alive. +{{% /alert %}} + ## Customizing Login Behavior Login behavior can be customized by implementing a custom Java action and registering it to be used instead of the default login action. To do this you need to perform the following steps, saving the updated Java in the `javasource` folder of your app. diff --git a/content/en/docs/refguide9/runtime/login-behavior.md b/content/en/docs/refguide9/runtime/login-behavior.md index c8ca7fac37a..cb53d8b8f60 100644 --- a/content/en/docs/refguide9/runtime/login-behavior.md +++ b/content/en/docs/refguide9/runtime/login-behavior.md @@ -22,6 +22,18 @@ In versions of Mendix below 9.11.0, the cluster manager will unblock *all* block Cluster manager behavior currently cannot be changed. {{% /alert %}} +## Blocked and Inactive Users and Existing Sessions + +Blocking a user, either automatically after failed login attempts or manually by setting the **Blocked** attribute of the user, only prevents that user from signing in again. It does not end sessions the user already has. This is deliberate: otherwise anyone could sign another user out by entering a wrong password for their account three times. + +Setting the **Active** attribute of a user to false does end their existing sessions. The session is ended on the user's next request, on every node of the cluster. + +If you block a user manually because they should lose access immediately, also set them to inactive or delete their sessions (`System.Session` objects associated with the user). + +{{% alert color="info" %}} +Ending the sessions of inactive users was introduced in Mendix 9.24.46. In earlier versions, an inactive user could keep using an existing session for as long as it was kept alive. +{{% /alert %}} + ## Customizing Login Behavior Login behavior can be customized by implementing a custom Java action and registering it to be used instead of the default login action. To do this you need to perform the following steps, saving the updated Java in the `javasource` folder of your app.