About error in PSM SAML

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

About error in PSM SAML

L4 Transporter

When I connect with PSM SAML through Balancer URL, f I connect to PSM02 instead of PSM01, I see the following errors. (Instead if I connect to PSM02 the connection works)

 

[28/10/2025 | 12:37:12.413397] | {pid= 4584} | {tid=   2692} | class CCAAccountDataLoader *    | PSM\CASessionCommonLib\CAAccountDataLoader.cpp(68)      | :: | PSMSC119I [PSMSAMLUser] Received password content successfully (Safe: PSM, Folder: Root, Object: PSMSAML)

[28/10/2025 | 12:37:26.319626] | {pid= 4584} | {tid=   2692} | class CPSMInfrustructureExceptionBase * | PSM\PSMInfrastructureLib\PSMInfrastructureExceptionBase.cpp(29) | :: | PSMIN001I PSM infrastructure library exception occurred. PSMIN103I Client pipe has disconnected. Code: 109 (Codes: -1, -1)

[28/10/2025 | 12:37:26.320940] | {pid= 4584} | {tid=   2692} | class CPSMSessionLogonRequestHandler * | PSM\PSMServer\PSMSessionLogonRequestHandler.cpp(226)     | :: | PSMSR1473W Session id: 3 is in error state and will be closed forcefully.

[28/10/2025 | 12:37:26.335316] | {pid= 4584} | {tid=   2692} | class CPSMSessionLogonRequestHandler * | PSM\PSMServer\PSMSessionLogonRequestHandler.cpp(230)     | :: | PSMSR1474E Failed to close forcefully session that is in error state (Session id: 3).

[28/10/2025 | 12:37:26.335392] | {pid= 4584} | {tid=   2692} | class CPSMBaseException *      | PSM\PSMServer\PSMBaseException.cpp(38)            | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 3) (Codes: -1, -1)

[28/10/2025 | 12:37:26.335459] | {pid= 4584} | {tid=   2692} | class CPSMBaseException *      | PSM\PSMServer\PSMBaseException.cpp(38)            | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR955E Failed to get the session uuid by session id (Session ID: 3). Reason: PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 3) (Codes: -1, -1)

[28/10/2025 | 12:37:26.335501] | {pid= 4584} | {tid=   2692} | class CPSMBaseException *      | PSM\PSMServer\PSMBaseException.cpp(38)            | :: | PSMSR009I Privileged Session Manager exception occurred. PSMSR923E Failed to remove the session parameters from the session in the session synchronizer (Session id: 3). Reason: PSMSR955E Failed to get the session uuid by session id (Session ID: 3). Reason: PSMSR893E Session id was not found in session synchronizer. Diagnostic information: 6, (Session id: 3) (Codes: -1, -1)

[28/10/2025 | 12:37:26.335537] | {pid= 4584} | {tid=   2692} | class CPSMSessionLogonRequestHandler * | PSM\PSMServer\PSMSessionLogonRequestHandler.cpp(270)     | :: | PSMSR927W Failed to handle the disconnection of the logon request for session id: 3. Reason: PSMSR923E Failed to remove the session parameter

3 REPLIES 3

L4 Transporter

Hi @simona vittori​  it seems session ID is not found when its try to make connection. does your LB set up with sticky session?

L4 Transporter

Hi @simona vittori​  it seems session ID is not found when its try to make connection. does your LB set up with sticky session?

L7 Applicator

Hi @simona vittori​ 

 

Please also check whether LB has a short idle timeout, it might be closing the connection while the PSM is processing the SAML credentials.

 

I would assume you would have already validate the connectivity to both the PSMs.

 

 

  • 119 Views
  • 3 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!