SecuRemote and Thinkpad ThinkVantage CSS Password Manager

[WildChappy]

Hello Everyone,

I am attempting to connect to a Secure Platform NGX Firewall with SecuRemote version NGX R60 HFA1 (Build 019).
I am trying to automate connecting using a new Lenovo ThinkPad T60 with its fingerprint scanner and Lenovo's ThinkVantage Client Security Solution Version 8.0

I setup the Password Manager to work with SecuRemote with a Username and Password for connecting. During the initial SecuRemote connection, the user connects to the VPN just fine. Then say you log out or reboot and attempt to connect SecuRemote for a second time and the Password Manager does was it is suppose to do, put the password into the proper fields and automaticly attempts to connect, however it fails with a bad username or password.

Ok, now you know the background, here is what I have found so far, If I change the password inside the CSS Password Manager Entry for my SecuRemote connection to what the password is suppose to be and attempt to connect with SecuRemote, the Password Manager fills the password correctly, however, the Password Manager seems to do a verify on the password it types in and all of a sudden a Password Manager window pops up asking about the password, The window says that the password has changed and it askes me if I want to save the new password into the Password Manager Entry for SecuRemote. If I say "yes", the next time you attempt to connect via SecuRemote your "Out of Luck" as the password is wrong. Now if you say "no" to that question, you will be able to connect to everytime!

Ok now for my questions.
Is SecuRemote somehow ciphering the password field so that the password that is typed is correct, however the one that actually shows in the field is bogus one? First, Why is Checkpoint doing that, and Second if they are, does anyone have a suggestion as to how I can get this to work so that the Password Manager does not have a fit everytime I attempt to connect to our network?
Note, I have a case into Lenovo ThinkVantage support for the problem, however have not been too productive getting them to come up with a fix.

Any Ideas?

Thanks for Looking!
WildChappy