MaxDynamicSessionsPerUser

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PAM Self-Hosted Articles
3 min read
L1 Bithead
No ratings

Question

The default setting for the number of Maximum Dynamic User Sessions Per User is 300.

How can this be changed ?

Answer

There are 3 parameters in the dbparm.ini file in the Vault that control the dynamic session mechanism

 

MaxConcurrentUsers - Specifies the maximum concurrent number of users to be able to login to the Vault.
MaxDynamicSessionsPerUser - Specifies the maximum concurrent number of sessions that a user can have to the Vault.
MaxDynamicSessionsTotal - Specifies the total number of dynamic sessions, can be used in order to leave free sessions for "regular" session IDs.

 

If these parameters are not specifically defined in dbparm.ini then the following are the default values:-

 

MaxConcurrentUsers = 3000
MaxDynamicSessionsPerUser = 300
MaxDynamicSessionsTotal = 3000

 

The minimum and maximum values are as follows:-

 

MaxConcurrentUsers = 3000-32000
MaxDynamicSessionsPerUser = 0-32000
MaxDynamicSessionsTotal = 0-32000

 

These parameters are connected.

 

When MaxDynamicSessionsPerUser is not set in dbparm.ini it is calculated according to MaxDynamicSessionsPerUser = MaxConcurrentUsers/10. This is the recommended ratio.
When MaxDynamicSessionsTotal is not set in dbparm.ini it is set to be equal to MaxConcurrentUsers.

 

So, the Maximum Dynamic User Sessions Per User value can be changed by either increasing the MaxConcurrentUsers value or by specifying the MaxDynamicSessionsPerUser in the dbparm.ini file.

 

PLEASE NOTE: 

  1. Changing the dbparm.ini file requires a vault restart for any parameter changes to apply
  2. Changing from default or recommended values may cause other vault performance issues
  3. Keep in mind that the default 300 session limit is set to limit the risk of DDOS attacks
  4. Ensure that a backup of the dbparm.ini file is available before making any changes.

 

Issue

Hello, Our automation is doing mass change via REST APi calls and we got the following error : @timestamp:2025-11-01 07:07:14.419 @version:1 agent.hostname:s0ab0rif agent.name:s0ab0rif agent.version:8.11.3 event.shipping.timestamp:2025-11-01 07:07:14.419 geo.name:we-region labels.assettag:901288491 labels.env:pro labels.location:mecccm2 labels.respteam:hpc - os and security labels.serverrole:none log.file.path:c:\windows\temp\pvwa\pvwa.app.log ls_collector:pwcb1 ls_env:prod message:2025-11-01 07:07:14,262 || WARN || 55 || || REST API || || 752b53db-1647-49f3-bc5c-d3001d0dd917 || Logon Response:: Code: 500. Content: {"ErrorCode":"ITATS163E","ErrorMessage":"The number of concurrent dynamic sessions for user jf32133 has reached its limit (350)."} || || AuthController message_orig:2025-11-01 07:07:14,262 || WARN || 55 || || REST API || || 752b53db-1647-49f3-bc5c-d3001d0dd917 || Logon Response:: Code: 500. Content: {"ErrorCode":"ITATS163E","ErrorMessage":"The number of concurrent dynamic sessions for user jf32133 has reached its limit (350)."} || || AuthController subtype:pvwa tags:_grokparsefailure topic:Idira _id:ta8GPpoBmgbGzbU3-W84 _index:cyberark-2025.10.09-000036 Please let me know how we can increase limit of concurrent dynamic sessions for that particular user

Environment

Password Vault Web Access Accounts
Rate this article:
  • 443 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:45 AM
Updated by: