February 2020 - Cloud Authentication Service

Action Recommended for Certain SSO Agent Deployments to Handle Google Chrome 80 Changes

On February 18, 2020, Google will slowly roll out a change to the cookie behavior in Google Chrome version 80 or later. This changed cookie behavior does not affect most RSA users. However, there is a possibility that users who have version 80 and authenticate to the RSA SecurID Access Application Portal might experience step-up authentication failure if the authentication session is longer than two minutes. This does not affect deployments that use RADIUS or relying parties. If this issue affects your users, you might need to take further action. For instructions, see Immediate Action Recommended for Certain SSO Agent Deployments to Handle Google Chrome 80 Changes.

Schedule for Planned Changes to Cloud Authentication Service IP Addresses (March 2020)

To align with changes required by our Cloud service provider, Microsoft Azure, the Cloud Authentication Service and Cloud Administration Console IP addresses will change in March 2020. RSA recommends that you make any necessary firewall changes to allow your identity routers and user browsers to connect to these new IP addresses. To prevent service disruption, your network must be able to connect to both the existing and new IP addresses by the following dates.

Region	New IP Addresses	Date
ANZ	20.37.53.30, 20.39.99.202	March 20, 2020
EMEA	51.105.164.237, 52.155.160.141	March 20,2020
US	52.188.41.46, 52.160.192.135	March 21, 2020

Note:  No configuration changes are required within the Cloud Authentication Service. If your firewall rules limit outgoing IP traffic, then you need to work with your IT team to add or whitelist the new IP addresses. If your firewall rules do not limit outgoing IP traffic, then you do not need to take additional action at this time.

To test access to the new IP addresses, see Test Access to Cloud Authentication Service.

These dates and IP addresses are also published here.

Support for Windows Hello and Android Phone as FIDO Authenticators

The Cloud Authentication Service supports Windows Hello and Android phone as FIDO authenticators. Users must register these authenticators in My Page and not during first-time authentication to an application. You must enable registration for these authenticators in My Page. For more information, see FIDO Authenticators.

New Terminology for Authenticators and Devices

With the support of the FIDO platform authenticators Windows Hello and Android phone, terminology is changing in the Cloud Administration Console and product documentation to address authenticators that are not necessarily devices.

The following changes have been made in the documentation:

• Authenticator is the new general term for something that a user authenticates with. As part of this change, device registration has been changed to authenticator registration. For example, "Users must complete authenticator registration to access protected applications."

• Device will continue to be used in situations specific to the RSA SecurID Authenticate app. For example, "An individual user can use the SecurID Authenticate app on a single registered device."

• The FIDO terminology has changed for end users in My Page, browser-based authentication prompts, and help. In the past, users selected FIDO Token in My Page or More Options, for example. Now users select security key, Windows Hello, or Android phone, depending on what your organization has instructed them to register and use.

  All FIDO authenticators are still managed by the FIDO Token authentication method in the Cloud Administration Console.

The Cloud Administration Console text will be updated in a future release.

New Identity Source Attribute – Alternate Username

A new user identifier, Alternate Username, is available as an identity source attribute. Customers with relying parties such as Azure Active Directory can use any attribute, such as UPN, that is suitable for use as the RSA SecurID Access username. For configuration instructions, see the "Add an Identity Source" section on Add, Delete, and Test the Connection for an Identity Source in the Cloud Authentication Service.

Cloud Administration API Retrieves Device Registration Codes

A new API allows users to securely register their devices within custom help desk and self-service portals. The API generates one-time device registration codes. For more information, see Cloud Administration Retrieve Device Registration Code API.

Fixed Issues

Fixed Issue	Description
NGX-38913	Previously, customers with the RSA SecurID Access Base or Enterprise Edition were unable to use access policies that contained condition attributes that are supported for those editions. This problem has been resolved.
NGX-38902	Previously, under certain conditions, some users continued to appear on the Users > Management page in the Cloud Administration Console and in synchronized user reports after their identity source had been deleted from the customer's deployment. This problem no longer occurs.

February 3, 2020 - SecurID Authenticate for Android App

RSA SecurID Authenticate 3.2 for Android contains bug fixes.

 

January 2020 - Cloud Authentication Service

FIDO2 Certification for Cloud Authentication Service

The Cloud Authentication Service is now a FIDO2 Certified Server. The certification demonstrates compliance with the FIDO specification and ensures compatibility with any FIDO-certified security key.

As part of this certification, the Cloud Authentication Service checks the integrity of the security key response message during registration. If the response message is modified on its way to the Cloud Authentication Service, the registration is unsuccessful.

Additionally, the Cloud Authentication Service verifies the integrity and authenticity of FIDO-certified security keys listed with the FIDO Alliance Metadata Service (MDS). The Cloud Authentication Service rejects MDS-listed keys if detected as counterfeit or compromised.

Jailbreak Detection for SecurID Authenticate for iOS

SecurID Authenticate 3.2 for iOS contains the following updates:

• Compliance checks to ensure the device is not jailbroken before allowing use of the app. If the Authenticate app detects that a device is jailbroken, the app displays a "Device Not Compliant" message and prevents use of the app. This message displays when users open the app (for example, to complete device registration or an authentication request) and in interactive notifications for Approve.

  If your users are using jailbroken devices, they will no longer be able to use the app. Instruct your users to restore their devices, and then complete device registration again with the RSA SecurID Authenticate app.

• Bug fixes.

Security Fix for Integrated Windows Authentication Connector Requires Manual Update

A password is now required to protect the Issuer Signing Certificate file (.pfx) when you install the Integrated Windows Authentication (IWA) Connector. If your company installed the Connector prior to the January 2020 release, RSA recommends that you install the latest version of the Connector (1.6) with the certificate file password. For instructions, see Install the Integrated Windows Authentication Connector.

Schedule for Planned Changes to Cloud Authentication Service IP Addresses (March 2020)

To align with changes required by our Cloud service provider, Microsoft Azure, the Cloud Authentication Service and Cloud Administration Console IP addresses will change in March 2020. RSA recommends that you make any necessary firewall changes to allow your identity routers and user browsers to connect to these new IP addresses. To prevent service disruption, your network must be able to connect to both the existing and new IP addresses by the following dates.

Region	New IP Addresses	Date
ANZ	20.37.53.30, 20.39.99.202	March 20, 2020
EMEA	51.105.164.237, 52.155.160.141	March 20,2020
US	52.188.41.46, 52.160.192.135	March 21, 2020

Note:  No configuration changes are required within the Cloud Authentication Service. If your firewall rules limit outgoing IP traffic, then you need to work with your IT team to add or whitelist the new IP addresses. If your firewall rules do not limit outgoing IP traffic, then you do not need to take additional action at this time.

To test access to the new IP addresses, see Test Access to Cloud Authentication Service.

These dates and IP addresses are also published here.

Known Issue

Known Issue	Description
NGX-38913	Problem: Customers with the RSA SecurID Access Base or Enterprise Edition cannot use access policies that contain condition attributes that are supported for those editions. Workaround: If you have the Base or Enterprise Edition, do not use conditional attributes in access policies until after this issue is fixed.

November 2019 - Cloud Authentication Service (Identity Router)

The November 2019 release includes the following features and benefits.

Identity Router Update Schedule and Versions

Identity routers will be updated according to the following schedule.

Date	Description
12/4/19	Updated identity router software is available to all customers.
1/25/2020	Default date when identity routers are scheduled to automatically update to the new version unless you modify the update schedule or update manually.
2/22/2020	If you postponed the default date, this is the last day when updates can be performed.

The new identity router software versions are:

Deployment Type	Version
On-premises	2.8.0.0.5
Amazon Cloud	RSA_Identity_Router 2.8.0.0.6

RADIUS Support for Emergency Tokencode

Emergency Tokencode is supported for thick RADIUS clients and for Cisco Adaptive Security Appliance (ASA). RADIUS users who forget or misplace their registered devices can access protected SaaS and web applications using Emergency Tokencode by selecting it from the list of available authentication options. You can also customize your Cisco ASA to accept Emergency Tokencode.

Note:  If you are planning to use Emergency Tokencode, perform the customization before you update the identity router.

For instructions, see Customize the RSA SecurID Access Web Interface for a Cisco Adaptive Security Appliance.

SAML Configuration Improvements

The following configuration improvements affect SAML-enabled web applications when the Cloud Authentication Service is the identity provider:

• You can require the identity provider to send AuthnContextClassRef in the SAML response as PasswordProtectedTransport to indicate that the password exchange must use a secure transport method. Currently, AuthnContextClassRef is sent as Password.

• You can configure multivalued attributes to send each value in a separate attributeValue element. Currently, these values are separated by commas.

For instructions, see Configure Advanced Settings for a SAML Connection.

Customizable Attribute Mappings for Active Directory Identity Sources

You are now allowed to customize the default attribute mappings for Active Directory identity sources. For more information, see Directory Server Attributes Synchronized for Authentication.

Improved Documentation for Access Policies

RSA Link now provides complete documentation describing how to use operators when specifying LDAP attributes in access policies. For more information, see Operators for Using LDAP Attributes in Access Policies.

Fixed Issues

Fixed Issue	Description
NGX-37423	When the Cloud identity provider was configured for RSA SecurID Access manages all authentication with Password as the primary authentication method, iOS auto-populated the password field with a suggested strong password and forced the user to choose a password. This problem no longer occurs and users are simply prompted to enter the email address and password.
NGX-37397	Previously, in environments that used the SSO Agent with a load balancer, when the load balancer checked the identity router health status and no alternate Cloud Authentication Service IPs were reachable, the identity router status servlet reported the identity router as unhealthy. As a result, load balancer stopped sending traffic to the identity router. This problem has been fixed.
NGX-37059	Previously, when domain certificates that had been uploaded to the Cloud Authentication Service expired, administrators were unable to navigate to other console pages, including the Authentication API Keys. Now, a warning message appears when certificates expire and navigation to other pages is allowed.
NGX-35793	Approve authentication through the MFA Agent was failing because inactive notifications were being sent to the user's device. This problem has been fixed.
NGX-34903	In some deployments, users were able to access SAML and Windows O365 applications directly with an expired LDAP password. Now, users are prompted to change their passwords when the option to allow password change is enabled.
NGX-34426	Previously, a security vulnerability was found in a version of jQuery-ui included in the identity router. The jQuery-ui was upgraded to a newer version to address this vulnerability.
NGX-33608	The security vulnerability affecting session fixation for the identity router setup console and web portal was fixed.

Known Issues

Known Issue	Description
NGX-16781	Problem: The identity router does not reliably route traffic to some services when multiple services are hosted by the same network resource. For example, if your DNS server and Active Directory server share the same IP address, the identity router might not route traffic properly to either service. Workaround: Configure DNS, gateways, and other network infrastructure services on dedicated servers that do not host other services for RSA SecurID Access.
NGX-38137	Problem: Multifactor authentication fails when a company (deployment) has the following configuration settings: The RSA SecurID Access Setup Administrator selected Allow access to Authenticate Tokencode, Approve, Device Biometrics and FIDO Token for the company. The resource is protected by a preconfigured access policy. Authentication fails with the message "No challenge methods found for given policy." Workaround: Use a custom access policy.

November 14, 2019 - SecurID Authenticate for Windows 10 App

RSA SecurID Authenticate 3.2 for Windows 10 allows a user to add up to 10 different accounts (formerly called companies) in the app and contains bug fixes.

October 2019 - Cloud Authentication Service

The October 2019 release includes the following features and benefits.

Enable Password-Less Authentication Using FIDO2 Tokens When Authenticating to Service Providers

You can now specify FIDO Token as a primary authentication option when configuring service providers. To authenticate with this option, a user must have a FIDO2 token that requires multifactor authentication on the token (such as PIN or biometric), the user must set up the token multifactor authentication, and the user must register the FIDO Token in My Page. For more information, see Cloud Authentication Service User Requirements.

Add Your Own Customized Logos to User Authentication Pages

You will be able to customize pages used for additional authentication by adding your own logo when you configure RSA SecurID Access My Page. For instructions, see Manage RSA SecurID Access My Page.

User Event Log API Provides Details on Users' Identity Confidence Scores

The Cloud Administration User Event Log API will return the overall identity confidence score, including threshold and category scores (behavior, location and device) for users. Previously this information was exposed only in the User Event Monitor. Through the API, you can now export user risk information to any Security Information and Event Management (SIEM) platform for further analysis. For more information, see Cloud Administration User Event Log API.

Full Support for Adding 10 Accounts in SecurID Authenticate App Releases

RSA SecurID Authenticate 3.1 for iOS allows a user to add up to 10 different accounts (formerly called companies) in the app and contains bug fixes. A November release of RSA SecurID Authenticate for Windows will allow a user to add up to 10 different accounts.

RSA is aware of the current iOS 13 issue in which the Touch ID screens do not display when a user is trying to authenticate with Touch ID on some devices. For example, this issue is noticed in the Authenticate app when a user is authenticating with a fingerprint to view the Authenticate OTP or to access an application.

Users should update to iOS 13.1.3 to resolve this issue. In the meantime, users can continue to use Touch ID in the Authenticate app by placing their fingers on the Home button when they would usually see the Touch ID screens. Touch ID is working in the background, so placing their fingers on the Home button completes the authentication request.

More Flexibility with New "Determined by Service Provider" Primary Authentication Option When Adding a Service Provider

To provide more flexibility when configuring authentication for a service provider, if you select the option to have RSA Authenticator manage all authentication, you can now select the Determined by Service Provider at Run Time option to specify primary authentication in the RequestedAuthnContext attribute. For more information, see Add a Service Provider.

Expanded Cloud Authentication Service Authentication Methods and Improved Productivity and Security with RSA MFA Agent for Microsoft Windows

RSA MFA Agent 1.2 for Microsoft Windows works with the Cloud Authentication Service to require users to provide additional authentication to sign into Windows computers, whether they are online or offline.

The main highlights include:

• Convenient authentication using Approve, Authenticate Tokencode, RSA SecurID Token, Device Biometrics, SMS Tokencode, Voice Tokencode and Emergency Tokencode.

• Seamless authentication using the same registered authentication device for both online and offline Windows sign-in.

• Online emergency access to Windows computers when users misplace or lose their authenticators (RSA SecurID Authenticate device or RSA SecurID hardware token).

• Support for policy-driven identity assurance with conditional trusted network and trusted location attributes.

• Many features to improve productivity and security during Windows sign-in.

For documentation and product download, see RSA MFA Agent for Microsoft Windows.

Fixed Issues

Fixed Issue	Description
NGX-33732	Previously, a customer was unable to export a large number of user event logs using the Cloud Administration User Event Log API. This problem has been fixed.
NGX-34352	Previously, when a new customer used a Firefox or Microsoft Edge browser to sign in to the Cloud Administration Console for the first time, the license did not display correctly. This problem has been fixed.
NGX-36891	Previously, you were not permitted to save a relying party configuration with an ACS URL of more than 100 characters. The limit has been increased to 4000 characters.

Known Issue

Known Issue

Description

NGX-16781

Problem: The identity router does not reliably route traffic to some services when multiple services are hosted by the same network resource. For example, if your DNS server and Active Directory server share the same IP address, the identity router might not route traffic properly to either service. Workaround: Configure DNS, gateways, and other network infrastructure services on dedicated servers that do not host other services for RSA SecurID Access.

September 2019 - Cloud Authentication Service

Cloud Authentication Service Phased Update Process

Cloud Authentication Service updates will be rolled out in phases for each region (ANZ, EMEA, US) between October 9-17, 2019. RSA will notify you before your region is updated.

Emergency Access Enhancements

To enhance emergency access capabilities, Emergency Tokencode will be available for users who forget or misplace their registered devices. After you generate the tokencode in the Cloud Administration Console, the user can select Emergency Tokencode during the next authentication. For more information, see Supported Authentication Methods - Emergency Tokencode.

Note:  In the September release, this feature is supported for SaaS and web applications only. Support for RADIUS applications is expected to be available in a future release.

Performance and Reliability Improvements

To help improve performance and reliability, the components responsible for backend communication in the Cloud will be updated.

Planned Update to Cloud Authentication Service IP Address Rescheduled

For more information on this update, see the RSA Link notification.

October 1, 2019 - SecurID Authenticate for Android

RSA SecurID Authenticate 3.1 for Android allows an individual user to add up to 10 different accounts (formerly called companies) in the app. Also, this release is qualified with Android 10.

September 18, 2019 - RSA SecurID Authenticate for iOS

RSA SecurID Authenticate 3.0.4 for iOS is qualified with iOS 13 and resolves NGX-34252, an issue with the Authenticate OTP display on iOS 13.

September 5, 2019 - SecurID Authenticate for Windows 10

RSA SecurID Authenticate 3.1.1 for Windows contains the following updates:

• To reduce administrative effort and increase usability, if a user’s email address changes in the identity source, the Authenticate app continues to work seamlessly. Users no longer need to re-register their devices.

• Bug fixes.

With this release, SecurID Authenticate for Windows no longer supports Windows Mobile devices.

August 2019 - Cloud Authentication Service

The August 2019 release provides the following features and bug fixes.

Generate a Device Registration Code for Users

Help Desk Administrators can use the Cloud Administration Console to generate a one-time numeric device registration code and provide it to users who need to register iOS, Android, and Windows devices with the RSA SecurID Authenticate App. This capability will help your company move closer towards meeting requirements for National Institute of Standards and Technology (NIST) Identity Assurance Level 2. To learn how to use this feature, see Manage Users for the Cloud Authentication Service - Generate a Device Registration Code.

Improved Single Sign-On Option When Adding a Service Provider

To improve usability, when you add a service provider and select to manage all authentication, you can now select a Cloud identity provider to provide the primary authentication. This is useful for providing single sign-on from RSA Authenticator or third-party portals or links.

Improvements and Additional Configuration Options for My Page

You can now provide single sign-on to My Page when users access My Page through the RSA Authenticator Application Portal, a third-party portal where My Page is configured, or directly through the My Page URL.

Additionally, to increase flexibility, RSA SecurID Access My Page now contains the following configuration options:

• Logout URL to redirect users to a specific URL after they sign out of My Page.

• Error URL to redirect users to a specific URL after they encounter an error.

• Assertion Consumer Service value for copying into your identity provider configuration settings if you are configuring My Page for single sign-on in an unsolicited response flow (for example, when users access My Page through a third-party portal).

For more information, see Manage My Page.

Additional Deployment Option for SecurID Authenticate for Windows

Generally, users install SecurID Authenticate for Windows from the Microsoft Store. If your users cannot use the Microsoft Store, you can use Deployment Image Servicing and Management (DISM) to deploy the app from a command-line tool. After the app is deployed, users can then complete SecurID Authenticate device registration.

For more information, see Deploying the RSA SecurID Authenticate for Windows App Using DISM.

Send Us Your Feedback

Do you have thoughts on that you want to tell us? Are you finding what you need in the documentation on RSA Link? It is easier than ever to send us your feedback.

• Go to https://rsalink.wufoo.com/forms/rsa-securid-suite-product-feedback/ to send feedback on , including Cloud Authentication Service and Authentication Manager.

• Click Tell us what you think of this page at the bottom of any Help content page on RSA Link to send us your feedback on our documentation.

We can't wait to hear from you!

Fixed Issues

Fixed Issue	Description
NGX-33217	Publishing in a cluster with a Global Server Load Balancer (GSLB) resulted in a HTTP status code 503 error for some customers. The documentation has been clarified to explain that if you use GSLBs, configure them to wait for seven minutes before they switch to another cluster. This guidance is now documented in Publishing Changes to the Identity Router and Cloud Authentication Service.

August 14, 2019 - RSA SecurID Authenticate for iOS App

RSA SecurID Authenticate 3.0.3 for iOS contains bug fixes.

Fixed Issue

Fixed Issue	Description
NGX-33118	SecurID Authenticate for iOS no longer freezes on the splash screen when receiving notifications.

 

Return to Release Notes Archive - Cloud Authentication Service and Authenticators.