---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Limit concurrent sessions across all nodes \[Updated in Security Center 1.3\]

# Limit concurrent sessions across all nodes \[Updated in Security Center 1.3\] {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Use the
glide.authenticate.limit.concurrent.sessions.across.all.nodes property
with the Limit Concurrent Sessions plugin to manage the number of sessions tracked across all
nodes.
When the [Limit concurrent sessions](https://servicenow-prod.fluidtopics.net/pRbP05s_aCRc2HUiX6X~UA "You can limit the number of concurrent interactive sessions for a user or role on an instance across all nodes.") plugin is active, the number of open
sessions can be limited per user. Ensure that when this plugin is active that the
(Glide authenticate limit concurrent sessions across all nodes)
property is set to true so that the number of open sessions are
tracked across all nodes instead of a single application node. If this property is set to
false, multiple sessions can be open across multiple nodes, which
increases the chances of session hijacking.

## More information {#sc-limit-concurrent-sessions-across-all-nodes__section_qhx_1b1_xwb}

{#sc-limit-concurrent-sessions-across-all-nodes__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | glide.authenticate.limit.concurrent.sessions.across.all.nodes |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true |
| Default value | true |
| Category | [Session management](https://servicenow-prod.fluidtopics.net/VAFB7gAR3D02VvnVYJ_a3g "This category looks at the security of the application state for a user. Sessions should be unique to each individual, unable to be guessed or shared, and invalidated after periods of inactivity or when not required. This includes factors such as cookie attributes for cookie-based sessions, session token generation, and storage and requirements for federated re-authentication.") |
| Security risk | * Severity score: 3.7 * CVSS score: Low * Security risk details: When using the Limit Concurrent Sessions plugin, setting this property to false enables multiple sessions across multiple nodes to be open which increases the chance of a security vulnerability like a session hijacking. {#sc-limit-concurrent-sessions-across-all-nodes__ul_g1g_3sf_xwb} |
| Dependencies and prerequisites | None |
| References | [Limit concurrent sessions](https://servicenow-prod.fluidtopics.net/pRbP05s_aCRc2HUiX6X~UA "You can limit the number of concurrent interactive sessions for a user or role on an instance across all nodes.") |
[ ]

{#sc-limit-concurrent-sessions-across-all-nodes__table_ajc_b43_3kb}