SecurID has an own PAM module that is configured in the /etc/pam.d/sshd .
The normal SSH connection works properly: at login it asks for a username and a PASSCODE that consists of a PIN+TOKEN.
However, the connection with the x2goclient doesn't work: after typing in the username and the PASSCODE it breaks down with the following message: "Access denied. Authentication that can continue: publickey,password,keyboard-interactive" .
I tried x2goclient from both windows (v4.0.3.2) and linux (x2goclient-4.0.1.4-1.el6.x86_64), both have the same issue.
First I though, that the SecurID PAM module changes the SSH password prompt (it is "enter PASSCODE :" instead of "password:") so I changed the prompt to the same as the normal SSH Password prompt: "Password:", but it didn't help.

In case of the x2goclient-cli Perl script, that comes with the x2goclient source, I found, that for a single x2go connection several (3-4x?) SSH connections are made in the background. In case of SecurID RSA, only the first SSH connection can work with a given PASSCODE, it is accepted only at the first SSH connection.
Perhaps the normal x2goclient behaves the same way: it tries to connect using the same PASSCODE several times, and this could be the cause of the problem.

Does anyone has some solution for this issue?

 

thanks

Swizzly