1 of 1 people found this helpful
is the nsh client you are using configured to use a nsh proxy?
is the appserver configured to use a nsh proxy?
check the secure files.
The NSH client is configured with NSH proxy but the app servers are not. That was the main reason for the difference in behavior. Once I updated the app servers to use ssoproxy, I saw the same behavior where the agent was seeing a different role for the “ls” activity using the following script.
Thanks for your assistance.