- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-15-2026 08:41 AM
I am seeing 401 Unauthorized (ITACM040S – User was automatically logged off from Vault) when calling GET /PasswordVault/API/Safes. I have kept limit as 1000 and timeout 10 mins.
This happens for Safes APIs everytime and for Accounts APIs sometimes. I am doing two calls to safes API at the same time, one to get safes data, and other to get the safe data to use that to get the safe Members data using safe id.
Is this expected behavior for more concurrent calls? In what scenario do we get this error? Want to know if this can be fixed by changing any implementation behavior or from the cyberark settings? Also is there any way to replicate the same error using postman?
Looking for answers or best practices from the community.
01-15-2026 08:46 AM
You might be running into problems with the concurrent calls . You can tell rest api that you will have concurrent sessions .
https://docs.cyberark.com/pam-self-hosted/latest/en/content/sdk/cyberark%20authentication%20-%20logon_v10.htm
concurrentSession
Set this parameter to True to enable the user to open multiple connection sessions simultaneously.
Up to 300 concurrent sessions are supported.
Type: Boolean
Mandatory: No
01-15-2026 09:01 AM
Thanks @Malcolm Murray
But will I be able to reproduce this error in postman to verify it? I am only able to reproduce the "ITACM020S" error and not the "ITACM040S" error.
Also wanted to know if I call multiple APIs quickly and parallelly then will it cause any errors?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

