AnsweredAssumed Answered

Authentication Manager 8.2 SP1 with Authentication Agent 7.2

Question asked by Arthur Chan on Mar 19, 2018
Latest reply on Mar 19, 2018 by Jay Guillette

Like • Show 0 Likes0
Comment • 5

Does anyone know if the combination of Authentication Manager 8.2 SP1, with RSA Authentication Agent 7.2 for Microsoft Windows is a known working combination? We are rolling out Win10 which will have Agent 7.3.3, but we want to avoid having to upgrade all of our existing Win7 (which have Agent 7.2) as the PC OS will be reinstalled soon anyway. Our Authentication Manager is currently at 8.1 SP1 which is soon going end of support.

I've combed through the documentation but cannot find any mention of what Agent versions are supported by AM 8.2 SP1.

No one else has this question

Outcomes

5 Replies

Erica Chalfin Mar 19, 2018 6:13 PM
Mark Correct
Correct Answer
Arthur Chan,

I think some of the information you need is available on the End of Product Support (EOPS) page for both
RSA Authentication Agent for Microsoft Windows and RSA Authentication Manager Appliance 8.x.

The end of product support for the RSA Authentication Agent 7.2 for Windows was June 2017. RSA Authentication Manager 8.1 SP1 goes into end of product support in December 2018.

While the 7.2 agent is still authenticating your users, as your see in your deployment, we would recommend coming up with an upgrade plan to 7.3.3 as you upgrade your users' operating systems to Windows 10.

Regards,
Erica
1 person found this helpful
Like • Show 1 Like1
Actions
- Arthur Chan @ Erica Chalfin on Mar 19, 2018 6:20 PM
  Mark Correct
  Correct Answer
  Thanks for the info, Erica! What you say makes sense - if I flip it around though, can you confirm that Agent 7.3.3 will work (and is supported) with AM 8.1 SP1? If I can postpone the AM upgrade until our Win10 rollout is completed that would be ideal also.
  
  Regards,
  Arthur.
  Like • Show 0 Likes0
  Actions
  - Jay Guillette @ Arthur Chan on Mar 19, 2018 6:47 PM
    Mark Correct
    Correct Answer
    Yes, agent upgrades and AM server versions are generally independent when talking about the good old, long standing SecurID protocol running on UDP port 5500.
    The Windows 7.2 agent only supported SSLv3, TLSv1.0 and TLSv1.1, not the newer TLSv1.2, so if you 'enforced' strict TLS v.1.2 on your AM servers, an 7.2 agent could not auto-register or get Offline Days, but it could authenticate
    But enforcing strict TLS is a configuration change at the command line, it is not a default, so a 7.2 agent would work OK with an AM 8.1 SP1 server
    An AM 8.1 SP1 base, no patches, also only supported SSLv3, TLSv1.0 and TLSv1.1, not the newer TLSv1.2. Support for TLS version 1.2 was added with Patch 3, and the capability to enforce only TLSv_1_2 came with Patch 14 and 15.
    The newer Windows 7.3 agents support all TLS versions and still support SSLv3.
    The 7.3.3[114] agent (and later) finally fix all those nagging Offline bugs, including the one where invalid proof is seen every 1 second. But this version won't be on Link for another week or so. In mean time open a support case for this version.
    1 person found this helpful
    Like • Show 1 Like1
    Actions
    - Arthur Chan @ Jay Guillette on Mar 19, 2018 6:53 PM
      Mark Correct
      Correct Answer
      Thanks for the detailed response, Jay! So, it sounds to me like Agent 7.3 will support AM 8.1 SP1 whether we have chosen to enforce TLSv1.2 or not.
      
      Regards,
      Arthur.
      Like • Show 0 Likes0
      Actions
      - Jay Guillette @ Arthur Chan on Mar 19, 2018 7:14 PM
        Mark Correct
        Correct Answer
        Yes, and without strict TLS on your AM server, you have breathing room to update any older 7.2 Windows agents, taking time to plan deployment roll out, maybe Win10 first, then hitting older Win7 agents that manifest problems like failure to download offline days.
        1 person found this helpful
        Like • Show 1 Like1
        Actions

Authentication Manager 8.2 SP1 with Authentication Agent 7.2

Outcomes

Related Content

Recommended Content