In the past I am having problem to get the next token mode working on ASA 8.0.3. We have users are using SSL vpn and authenticate via RSA server. If users type in the token incorrectly, it should prompt for waiting the next token mode. Have not upgrade my ASA to 8.0.4 yet but would like to know if ASA 8.0.4 does support next token mode.
Thank you for the reply. I just tested yesterday on 8.0.4 code and still not getting the next token mode. I am not sure what did I do wrong. I am not the admin of the RSA box but on the ASA I have the group of webvpn pointing to RSA with SDI protocol for authentication and still no good. Can you share your point. I appreciated.
We are using a mix of the traditional IPSec client and the new AnyConnect client on our ASA. I have authentication configured to communicate with the RSA server specifying SDI protocol. And our users do get the next token mode prompt.
Unfortunately the group of this users are using clientless and it would be nice to get the next token mode working. This was testing on the 5505 box. Interesting, I just tested the IPsec client version 5.0.03 with RSA authentication on the main ASA 8.0.3 code and no next token mode so tonight the main ASA is going to be upgraded to 8.0.4 code and I can test with the ipsec client. As for clientless, I just have to dig some more.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :