AutoLogonSequence

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

AutoLogonSequence

L1 Bithead

Hello Everyone,

 

I am using below AutoLogonSequence for some unix account which is require privilege. But its working extremely slow. I am also facing the same scenario in WinSCP sessions. There is no network issue. Any suggestion for that?

 

.*\@.*~>sudo su -

.*\@.*:>{Password}

 

Thanks

1 accepted solution

Accepted Solutions

L2 Linker

It may also be worth checking the ShellPromptForAudit setting on the Connection Component. PSM will attempt to match that pattern against the prompt after going through the AutoLogonSequence process.

 

PromptTimeout will determine how long it waits for that prompt, and TerminateOnShellPromptFailure determines whether it allows interaction after failing to find the prompt.

 

If it fails to match the prompt, and TerminateOnShellPromptFailure is No, it would present as a long pause after authentication before the user can interact with the session.

 

You can use a regular expression testing site to check whether the prompt matches the pattern.

View solution in original post

6 REPLIES 6

L7 Applicator

Hi @Burhan Alperen Arar​ 

 

Please run the exact same commands manually in an SSH session from the PSM server. If manual execution is slow, the issue might be on the target Unix machine and if sudo su - takes time, check authentication logs on the Unix system.

 

Try to adjust PSM session timeout values.

 

Also check server performance of PSM.

 

Hope it helps !

 

 

L2 Linker

It may also be worth checking the ShellPromptForAudit setting on the Connection Component. PSM will attempt to match that pattern against the prompt after going through the AutoLogonSequence process.

 

PromptTimeout will determine how long it waits for that prompt, and TerminateOnShellPromptFailure determines whether it allows interaction after failing to find the prompt.

 

If it fails to match the prompt, and TerminateOnShellPromptFailure is No, it would present as a long pause after authentication before the user can interact with the session.

 

You can use a regular expression testing site to check whether the prompt matches the pattern.

L1 Bithead

Hi Malhar & Henning

 

ShellPromptForAudit is : ".* " I assume it covers everything. So should i decrease the PromptTimeout value or change the ".*" to make it faster?

 

When I go directly the server and type sudo su its working fine. There is no performance issue with our psm servers as well

 

Thank You

L2 Linker

".* " should cover everything (unless the prompt doesn't end with a space) so it's probably not that. Could you provide a little more detail on where the slowdown is?

  • before sudo
  • during the sudo process
  • after the auto logon sequence
  • during normal operation

L1 Bithead

Hi Henning,

 

Actually i gave wrong information. When I put the {Username} after sudo su its working slow. But the only sudo su - is working fine.

 

Customer is accepted the sudo su - 🙂

 

Thank you for your assists

L4 Transporter

Hi @Burhan Alperen Arar​ 

 

Since several community members answered your question, please let us know if these solutions addressed your query.

If so, it would be great if you could mark the most helpful response as 'Select as Best' to assist other community members with similar questions.

 

Thank you, Liad.

  • 1 accepted solution
  • 6 Views
  • 6 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!