Authentication Issues Using A Third-Party RDP Client And RSA Authentication Agent 7.3.3 for Windows
Originally Published: 2018-07-23
Article Number
Applies To
RSA Product/Service Type: Authentication Agent for Windows
RSA Version/Condition: 7.3.3
Platform: Windows
Issue
Cause
Resolution
RSA will implement a new behavior and policy that allows customers to restrict the RSA Credential Provider's support for Connected Authenticator authentications to local sessions (only). This policy will be added to the RSA Authentication Agent's GPO templates and be documented in the RSA Authentication Agent for Microsoft Windows Group Policy Object Template Guide for the next release of RSA Authentication Agent for Windows software.
NOTE: No timeframe has been set for the next release of RSA Authentication Agent for Windows software as this is still under development however when the next version is released a product advisory will be posted at URL https://community.rsa.com/community/products/securid/advisories. Where customers have an RSA link account and can logon to RSA link they can follow this product advisory page by clicking the 'Following' drop-down selection (next to Actions) and click the Following option.
Related Articles
Increasing the number of connections from RSA Authentication Agent 7.3.x for Windows to a Windows platform with RDP 63Number of Views How does Remote Desktop handle Smart card and NLA? 75Number of Views Remote Desktop Protocol Vulnerability MS12-020 17Number of Views RSA SecurID prompt does not appear when connecting with Remote Desktop Protocol RDP on Microsoft Windows Server 2019 with … 55Number of Views How to enable Active Directory diagnostic event logging. 29Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle
Don't see what you're looking for?