How to resolve PSMApp authentication issue?

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

How to resolve PSMApp authentication issue?

L1 Bithead

We are experiencing an issue with CyberArk at the moment. PSM App_Server account authentication fails for some reason. I tried resetting the block on the Vault side, but it didn't work. I have seen logs about lack of disk space in the past, but now there is plenty of space. Additionally, the PSM was recently patched. Can you suggest a solution?

The error 257:

PSMSR037E Privileged Sessions Manager has been terminated. (Diagnistic information: PSMSR100E Failed to get new Privileged Session Manager session.Error ITATS004E Authenticaion Failure for User PSMApp_Server

1 accepted solution

Accepted Solutions

L1 Bithead

It works now,

the link helped me a lot: https://community.cyberark.com/s/article/PSM-update-credential-files

View solution in original post

11 REPLIES 11

L2 Linker

Does it happen frequently? Have you tried to reset password for this user with createcredfile tool?

L3 Networker

Does it happen frequently? Have you tried to reset password for this user with createcredfile tool?

L3 Networker

Does it happen frequently? Have you tried to reset password for this user with createcredfile tool?

L1 Bithead

Hi, Pkalina.

 

It occurs every time Cyberark Privileged Session Manager starts, which eventually fails to start.

 

I apologize for my ignorance, but I haven't attempted to reset the password for PSM App_Server, since I can't locate that user in Active Directory or PSM. It appears that the only place it exists is in the Vault. Can I just use the empty password? Both PSM Admin and PSM Connect seems to be working, but they are exist in Active Directory, unlike PSM App_Server.

This is an internal, vault user which works transparently and "connects" PSM with Vault. There is no option to have this user in AD (opposite to PSMConnect which can be Windows Local or AD account).

 

Login to PrivateArk console, navigate to User and Groups and check for PSMAppUsers group, when highlighted you should see a list for PSM App users, which will be equal to amount of installed PSM and PSMP instances. Empty password should not work, but this depends on passparm.ini file, in which you can specify the password policy for internal Vault accounts.

 

For procedure on how to reset password please refer to docs. Depending on PAS version, it is a bit different, as CyberArk changed this recently.

 

You should also check if this account is not locked - check the Trusted Are Network option in PrivateArk.

This is an internal, vault user which works transparently and "connects" PSM with Vault. There is no option to have this user in AD (opposite to PSMConnect which can be Windows Local or AD account).

 

Login to PrivateArk console, navigate to User and Groups and check for PSMAppUsers group, when highlighted you should see a list for PSM App users, which will be equal to amount of installed PSM and PSMP instances. Empty password should not work, but this depends on passparm.ini file, in which you can specify the password policy for internal Vault accounts.

 

For procedure on how to reset password please refer to docs. Depending on PAS version, it is a bit different, as CyberArk changed this recently.

 

You should also check if this account is not locked - check the Trusted Are Network option in PrivateArk.

This is an internal, vault user which works transparently and "connects" PSM with Vault. There is no option to have this user in AD (opposite to PSMConnect which can be Windows Local or AD account).

 

Login to PrivateArk console, navigate to User and Groups and check for PSMAppUsers group, when highlighted you should see a list for PSM App users, which will be equal to amount of installed PSM and PSMP instances. Empty password should not work, but this depends on passparm.ini file, in which you can specify the password policy for internal Vault accounts.

 

For procedure on how to reset password please refer to docs. Depending on PAS version, it is a bit different, as CyberArk changed this recently.

 

You should also check if this account is not locked - check the Trusted Are Network option in PrivateArk.

L1 Bithead

It works now,

the link helped me a lot: https://community.cyberark.com/s/article/PSM-update-credential-files

Good, nicely described.

For version >12.0 there is an additional mandatory parameter that needs to be used and also a pattern for command is different.

Good, nicely described.

For version >12.0 there is an additional mandatory parameter that needs to be used and also a pattern for command is different.

Good, nicely described.

For version >12.0 there is an additional mandatory parameter that needs to be used and also a pattern for command is different.

  • 1 accepted solution
  • 1546 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!