Hi everyone,
We’re encountering an issue while configuring the Password Capture Agent in our infrastructure.
We have a setup with two nodes running the AppServer behind an AWS Application Load Balancer.
When accessing the application via browser through the Load Balancer, everything works as expected — we can log in, view logs, and interact with the application normally.
However, when attempting to configure the PCA component via the Load Balancer, the wizard fails with an error (attached pic).
On the AppServer side, we observe the attached log entries:
2025-10-20 15:55:30.7687 INFO (AppServer): Could not find authentication data for session jSQugbnqF6QbSHU3KQ5d, it may have expired. 2025-10-20 15:55:30.7687 ERROR (ObjectLog Global): [ServiceStack.HttpError] 401 ServiceStack.HttpError: 401
As part of our troubleshooting, we disabled one of the two AppServer nodes.
In this configuration, the PCA wizard completes successfully, which suggests the issue may be related to session persistence across nodes.
We’ve attempted to configure sticky sessions on the AWS Load Balancer using both application-based cookies (specifically the ss-id) and Load Balancer cookies, but the issue persists.
Could you please advise on the correct Load Balancer configuration to support PCA setup in a multi-node AppServer environment?
Any guidance on session handling or specific cookie settings required for PCA would be greatly appreciated.