Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
12 changes: 12 additions & 0 deletions content/en/docs/refguide/runtime/login-behavior.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
12 changes: 12 additions & 0 deletions content/en/docs/refguide10/runtime/login-behavior.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
12 changes: 12 additions & 0 deletions content/en/docs/refguide9/runtime/login-behavior.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down