![]() It expects the earlier "RSA Security EAP" method, which can be added in the same Routing and Remote Access Policies policy window in which "RSA EAP - Protected OTP" was added. The windows authentication agent 6.1 software, can use the "RSA EAP - Protected OTP" method, but the Mac OS X VPN client software cannot. On page 15, step 18 of the guide, when you are configuring your Routing and Remote Access Policies, you are instructed to add only "RSA EAP - Protected OTP" to the "EAP Methods" of your VPN users policy. The RSA SecurUD / ISA 2006 implementation guide published by RSA covers what is necessary to connect using the RSA Authentication Agent 6.1 for Windows client software, but leave out a crucial step that allows the Mac OS X client to connect as well. RSA support was absolutely no help in the matter. The Mac OS X 10.3-10.5 VPN clients have a "SecureID" option, but failed immediately upon connection. ![]() Users authenticate using a username and an RSA SecurID 700 token. Similar to DotComCTO, I am using RSA Authentication Manager 6.1 along with Microsoft ISA 2006 its PPTP VPN. I don't know if this will help any of the original posters, being a year and a half later, but maybe it will help others in the future. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |