[munit_si@yahoo.com]

Originally Posted by zencoder

Do you have to use RSA Radius? VPN-1 natively supports the RSA API. You'll have to look up specific doco on your versions (you didn't tell us what you use), but I use it in this exact manner all the time. As a radius client, you may lose a lot of that functionality with RSA.

SecureClient has a fairly ugly response screen, prior to R56, but it works.

Screen shot of my XP Pro virtual machine being prompted, after I put my token into Next Tokencode Mode. Note the mis-labeling of the information being asked for. Specifically, in the RSA doco, PASSCODE = PIN + Tokencode, where TOKENCODE = 6 digits on the screen (or whatever your device supports...maybe more or less than 6...but I doubt it.) In this instance, RSA is asking for the next TOKENCODE, not the next PASSCODE...but it is such a minor difference that its not worth it to make a fuss.

Hi Zencoder,

Thanks a lot for the inf. In my test enviornment I am using RSA ACE server radius, not the one natively supported by VPN-1. I am having checkpoint R55.
I know secureId client prompts, but my problem is related to Admin logging to any CMA(launch SmartDashBoard, etc...) that time will the checkpoint promt for next tokencode mode if rsa falls for next token code mode for that user.

any suggestions/ideas on the same


You are rt , secureclient should prompt for tokencode rather then pass code, it could be GUI bug.