---
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 plugin

# Limit concurrent sessions plugin {#ariaid-title1}

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

Configure the com.glide.limit.concurrent.sessions plugin to reduce the chance of session hijacking on your instance.
When the Limit Concurrent Sessions (com.glide.limit.concurrent.sessions) plugin is not active, the glide.authenticate.limit.concurrent.interactive.sessions property is not set to true, or
the glide.authenticate.max.concurrent.interactive.sessions property is set beyond an organizationally-defined threshold, then ServiceNow instance user accounts are not limited to a defined number of concurrent
interactive sessions.  
1. Navigate to AllSystem DefinitionPlugins.
2. Find and select the Limit Concurrent Sessions plugin. The plugin ID is com.glide.limit.concurrent.sessions
3. On the System Plugin form, review the plugin details and then select the Activate/Upgrade related link.
4. Select Activate.
5. After the plugin has successfully activate, navigate to AllSystem PropertiesAll Properties.
6. Open the glide.authenticate.limit.concurrent.interactive.sessions system property, and set the value to true.
7. Open the glide.authenticate.max.concurrent.interactive.sessions system property, and set the maximum concurrent sessions. This value depends on the needs of your organization.
{#sc-limit-concurrent-sessions-plugin__ol_qyj_nbz_vgc}

## More information {#sc-limit-concurrent-sessions-plugin__section_qhx_1b1_xwb}

{#sc-limit-concurrent-sessions-plugin__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | * com.glide.limit.concurrent.sessions (plugin) * glide.authenticate.limit.concurrent.interactive.sessions(system property) * glide.authenticate.max.concurrent.interactive.sessions(system property) {#sc-limit-concurrent-sessions-plugin__ul_pzf_hcz_vgc} |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | * plugin * system property (Boolean) * system property (Integer) {#sc-limit-concurrent-sessions-plugin__ul_h2y_r2w_zgc}plugin |
| Recommended value | * com.glide.limit.concurrent.sessions is enabled * glide.authenticate.limit.concurrent.interactive.sessions system property set to true * glide.authenticate.max.concurrent.interactive.sessions set to a numeric value depending on the needs of your organization. {#sc-limit-concurrent-sessions-plugin__ul_wfb_p2w_zgc} |
| Default value | None |
| 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: A greater number of open sessions means there are more sessions that could potentially be hijacked. Limiting the number of allowed sessions per user is helpful in limiting risks related to denial-of-service (DoS) attacks. {#sc-limit-concurrent-sessions-plugin__ul_g1g_3sf_xwb} |
| Dependencies and prerequisites | None |
[ ]

{#sc-limit-concurrent-sessions-plugin__table_ajc_b43_3kb}