[vpn-help] VPN Client 2.2.2 Release Now Available ...

[Matthew Grooms]

On 7/1/2013 7:55 AM, Gerd Röthig wrote:
> Dear all,
>

Hi Gerd,

> thank you very much for your efforts in developing this new release.
>
> Unfortunately, there seem to have been some changes in the
> authentication procedure which render this new release unusable when
> users will have to use a password provided by a hardware token (such as
> Entrust or RCA).
> Scenario is as follows: For logging into the VPN, users will have to
> provide a 4-digit PIN number, follwed by an 8-digit number provided by
> the hardware token.

Is that 3 different logins, or is that one long password made from 
concatenating 3 different values?

> This login procedure works without problems in the 2.1.7 release.
>

Ok.

> The new 2.2.2 release, however, seems to fail transmitting these
> credentials properly. Apparently, it then seems to repeat that faulty
> login procedure several times, which finally results in the user's
> Entrust account being blocked because of too many login failures.
>
> The option to try to re-connect after a disconnect, should therefore NOT
> be made the default setting after installing the 2.2.2 Shrew Soft VPN
> client.
>

The login behavior should not have changed unless you check the option 
in the VPN Access Manager.

> Kind regards,
>

Thanks,

-Matthew