These release notes include product updates and bug fixes:
For additional information, see:
RSA SecurID Access Product Release Notes, a portal to all release notes for the Cloud Authentication Service, RSA Authentication Manager, authentication agents, and token authenticators.
Cloud Authentication Service Known Issues, an up-to-date list of known issues for the Cloud Authentication Service.
RSA Link, to access all RSA SecurID Access product documentation.
The March 2019 release includes the following features and bug fixes.
The latest identity router software versions are:
|Amazon Cloud|| |
Identity routers will be updated to these versions according to the following schedule.
|March 23, 2019||Updated identity router software is available to all customers.|
|May 25, 2019||Default date when RSA will send updates to all customers.|
|June 22, 2019||If you postponed the default date, this is the last day when updates can be performed.|
RSA SecurID Access has significantly improved the replication of critical data across identity routers for SSO Agent deployments. This critical data includes user profiles (keychains), user sessions, and cookies used for LDAP connections.
To take advantage of this new functionality, you must update all of your identity routers within a cluster at the same time and update all clusters at the same time. Perform simultaneous updates to avoid breaking inter- and intra-cluster keychain replication. After updates are complete, you will not be able to restore backup files created using the previous version. RSA recommends that you create backups immediately after performing the update.
Just-in-time synchronization is now automatically enabled for all customers who deploy the Cloud Authentication Service after the March 2019 release is available. Before March 2019, you needed to contact RSA Customer Support to enable this feature. Now Super Admins can enable it in the Cloud Administration Console on the My Account > Company Settings > Company Information tab without contacting Customer Support. If you are an existing customer and just-in-time synchronization was enabled prior to March 2019, it remains enabled until you choose to disable it.
Just-in-time synchronization ensures that the identity source in the Cloud Authentication Service is updated every time a user attempts to register a device using the RSA SecurID Authenticate app or access a protected resource using additional authentication after the LDAP password is validated. When this feature is enabled, you never need to add user records through manual or scheduled synchronization. For more information, see Identity Sources for the Cloud Authentication Service.
You can control whether users who are identified as high risk can access protected resources or if these users must authenticate at a higher assurance level than other users. Users might be identified as high risk because their accounts have been compromised, or because a third-party security information and event management (SIEM) solution, such as RSA NetWitness, has found suspicious activity. Use the Add/Remove High Risk User API to identify high risk users within the Cloud Authentication Service. Access policies provide a new condition attribute, High Risk User List, so that you can configure authentication requirements for high risk users. You can also use the Retrieve High Risk User List API to retrieve a list of all users identified as high risk. For more information, see:
If your company deploys RSA NetWitness Respond Version 11.3 or later, use that product instead of the APIs to obtain the same benefits. For instructions, see NetWitness Respond Configuration Guide for Version 11.3.
You can ensure that each Administration API has permission to access appropriate information in the Cloud Authentication Service by assigning an administrative role to each API key. The API uses the key in the request. By default, all Administration API keys generated before March 2019 default to the Help Desk Administrator role. The new Add/Remove High Risk User API and Retrieve High Risk User List API require keys assigned to the Super Admin role. For more information, see Using the Cloud Administration REST APIs.
The FIDO Token authentication method is now available on more browsers (including mobile browsers) and supports the FIDO 2 authentication standard. For a list of supported browsers, see Cloud Authentication Service User Requirements.
If the identity router is unable to connect to the Cloud Authentication Service (for example, during setup), you can use the Identity Router Setup Console to enable these emergency troubleshooting features:
Secure Shell (SSH) to access the command line
Emergency debug logging
After troubleshooting is completed and the identity router is connected to the Cloud Authentication Service, you can disable these features and use the Cloud Administration Console for future troubleshooting. For more information, see Troubleshoot Identity Router Issues.
You can create custom RADIUS profiles that specify an access policy rule set to identify which users can authenticate through the clients associated with the profile. Custom profiles increase flexibility because you can associate multiple profiles with a single client or the same profile with multiple clients. This feature allows you to implement strong, policy-based granular controls (for example, for Active Directory groups) for users and administrators who access RADIUS-based applications. For more information, see Configure a RADIUS Profile for the Cloud Authentication Service.
Status indicators for the identity router have been improved and expanded, making it easier for you to troubleshoot problems with identity router services, as well as connectivity problems between identity routers and the Cloud Authentication Service. You can view detailed status information for each identity router in the Cloud Administration Console on the Platform > Identity Router page. For more information, see View Identity Router Status in the Cloud Administration Console.
To align with the Google migration to Firebase Cloud Messaging (FCM), RSA SecurID Authenticate 2.2.0 for Android now uses FCM for push notifications. Users must take action by updating to version 2.2.0 or higher of the app by March 31, 2019.
NGX-18781. Previously, after you modified cluster relationships and published the changes, all identity routers in the clusters were restarted and the publish operation did not complete. The restart no longer occurs and publishing completes as expected.
NGX-21183. When you use the Identity Router VM Console to update network settings or recommit changes, static routes that were configured in the Cloud Administration Console are no longer deleted from the identity router.
The February 2019 release includes the following features and bug fixes.
Note: The current version of the identity router, v126.96.36.199.5, was not updated in this release.
Disaster Recovery Environment for the EMEA and AUS Regions
The disaster recovery environment for the Cloud Authentication Service is now available for the EMEA and AUS regions. When the Cloud Authentication Service environment becomes unavailable for any reason, your deployment automatically switches to the disaster recovery environment. RSA recommends that you test access to this environment before it is needed to ensure a smooth transition during unexpected downtime. For instructions, see Test Access to Disaster Recovery Environment.
On-Demand Access to Uptime Status of Cloud Services
You can now monitor the current and historical uptime of the Cloud Authentication Service and the Cloud Administration Console on a service status page. This page includes current service availability, recent uptime percentage, and historical uptime percentage. For more information, see Monitor Uptime Status for the Cloud Authentication Service.
Receive Frequent Updates on Cloud Authentication Service Availability with Health Check API
If you want to receive frequent updates on the Cloud Authentication Service availability, you can use the Health Check API to integrate with your application monitoring product. For more information, see RSA SecurID Access Health Check API.
Updated RSA SecurID Authenticate Apps Simplify Device Registration with EMM Technology
RSA SecurID Authenticate 2.3.0 for Android and RSA RSA SecurID Authenticate 2.2.0 for iOS now support simplifying device registration with Enterprise Mobility Management (EMM) technology that supports the AppConfig Community standards, such as VMWare AirWatch. With this functionality, you can help reduce the costs of device registration in your company by automatically downloading the app to users' devices and optionally configuring the Company ID and Email Address values. For more information, see Deploying the RSA SecurID Authenticate App in EMM Environment.
These app releases also contain bug fixes.
Users Must Update Their RSA SecurID Authenticate for Android App by March 31, 2019
To align with the Google migration to Firebase Cloud Messaging (FCM), RSA SecurID Authenticate 2.2.0 for Android uses FCM for push notifications. Users must take action by updating to version 2.2.0 or higher of the app by March 31, 2019.
NGX-21223. If you update the protected domain name after it has been initially configured on the My Account > Company Settings > Company Information page in the Cloud Administration Console, authentication no longer fails when users who access the RSA SecurID Application Portal attempt to open a Microsoft Office 365 application.
RSA SecurID Authenticate 2.2.1 for Android resolves an issue with app instability on Samsung devices running Android 9 Pie. Samsung users should upgrade to this app version.
To align with the Google migration to Firebase Cloud Messaging (FCM), RSA SecurID Authenticate 2.2.0 for Android now uses FCM for push notifications. Users must take action by updating to version 2.2.0 or higher of the app by March 31, 2019.
RSA SecurID Access added four new Administration APIs to help you expand the integration of Help Desk functions into your existing enterprise service desk tools. These APIs can be used to synchronize a user between an identity source and the Cloud Authentication Service, update a user's Enabled/Disabled status, find a user by searching for a string in the user's email address, and mark an inactive user as pending deletion or remove the marked deletion status. Also, the Retrieve Authentication Audit Logs API now supports filtering authentication audit logs using a specified date range. For more information, see:
To increase the usability on mobile browsers, the look and feel of the end-user authentication experience has been improved. One key change is the checkbox that displayed the contents of fields (for example, a passcode or tokencode field) has been replaced with a visibility toggle. For a list of supported browsers, see Cloud Authentication Service User Requirements.
To help improve security and increase flexibility, you can now specify if you want users to delete their devices in My Page. You configure this option in the Cloud Administration Console in Platform > My Page.
The Cloud Authentication Service now supports Active Directory 2019 as an identity source.
Disaster Recovery Environment Available for US Region
RSA maintains a disaster recovery environment for the Cloud Authentication Service. When the Cloud Authentication Service environment becomes unavailable for any reason, your deployment automatically switches to the disaster recovery environment. The disaster recovery environment is currently available for the US region. RSA recommends that you test access to the disaster recovery environment before it is needed to ensure a smooth transition during unexpected downtime. For instructions, see Test Access to Disaster Recovery Environment.
NGX-22022. Previously, when you used the Cloud Administration Console to add a SAML application, on the Connection Profile page, the Identity Provider URL field was not automatically populated if one identity router in the cluster was inactive. Now, if high availability is enabled for the cluster, the Identity Provider URL includes the load balancer name. If high availability is disabled, the URL includes the identity router hostname.
NGX-21728. Previously, some blocks of user data were too large to be successfully synchronized to the Cloud Authentication Service. The service has been modified to accept larger blocks of user data, so this problem no longer occurs.
NGX-21682. RSA SecurID Access has updated the list of country codes it supports for SMS Tokencode and Voice Tokencode authentication.
NGX-21553. Previously, authentication failed after an administrator re-mapped identity source attributes after the initial mapping. This problem has been corrected and mapping changes are now handled as expected.
NGX-21286. Previously, a misleading message indicating successful synchronization appeared in the administration audit logs after an administrator initiated identity source synchronization. The message has been corrected to reflect what actually happened: <Administrator_name> manually initiated synchronization for <identity source>.
NGX-20908. Previously, in certain deployments, after an administrator attempted to delete or edit and save an access policy, a publish operation succeeded to the identity routers but failed to the Cloud Authentication Service. This problem has been fixed.
Deploy Identity Routers in the Cloud Using Amazon Web Services
You can now deploy the identity router in the Amazon Web Services (AWS) Elastic Compute Cloud (EC2), thus reducing or eliminating the on-premises footprint of RSA SecurID Access. You have the flexibility to choose a cloud-only or hybrid-cloud deployment. For example, in a hybrid-cloud deployment, the identity router in the AWS cloud can connect to on-premises components such as RSA Authentication Manager or your LDAP directory server. You use an Amazon Machine Image (AMI) that you access with your AWS account to deploy the identity router in the cloud. For more information, see Amazon Web Services Identity Router Deployment Models.
Users Can Delete Registered Devices in My Page
To increase user self-service capabilities and reduce administrative support costs, My Page now allows users to delete their current registered devices. When users get new devices (for example, mobile phones) they can first delete their current devices in My Page and then complete registration on the new devices—all without administrative assistance.
New Administration APIs Available to Integrate Help Desk Functions Into Your Existing Tool Framework
RSA SecurID Access provides new Administration APIs to help you integrate RSA SecurID Access Help Desk functions into your existing enterprise service desk tools. The new APIs support the ability to retrieve user and device details, unlock tokencodes, delete user devices, update SMS Tokencode and Voice Tokencode phone numbers, and retrieve authentication audit logs for specific users. For more information, see Using the Cloud Administration REST APIs.
Improved Documentation for Configuring High Availability Deployments
You will find it easier to configure high availability for different types of deployment using improved documentation on RSA Link. High availability increases the likelihood that an identity router will be available to process authentication requests when one or more identity routers in the same cluster are down. High availability also improves performance by ensuring that requests are distributed evenly among identity routers. For instructions, see Configure High Availability for Cloud Authentication Service Deployments.
Updated RSA SecurID Authenticate Apps
RSA SecurID Authenticate 2.1.0 for iOS and RSA SecurID Authenticate 2.1.0 for Android contain bug fixes.
NGX-19853. When you disable a user, the RSA SecurID Authenticate for iOS and Android apps no longer delete the user's company in the app.
NGX-19870. When an automatic Integrated Windows Authentication (IWA) identity provider is configured in your deployment and users try to open the application portal URL in a browser, the portal sign-in page used to appear instead of the portal landing page that lists the applications. This problem has been fixed and now the portal landing page appears.
NGX-20598. Previously, when you attempted to add a location to the Trusted Location page using an address, certain addresses did not appear in the Bing maps suggestion list. Now you can use the Search button to find addresses that do not appear in this list.
Easier Direct-to-Cloud Integration for Key Apps
To provide easier direct-to-cloud integration, you can now protect Workday, ServiceNow, and Microsoft Office 365 without needing to use the SSO Agent. For instructions, see the following:
Updated RSA SecurID Authenticate for Android App
RSA SecurID Authenticate 2.0.2 for Android contains bug fixes.
NGX-17695. Previously, in some SSO Agent deployments, the publishing status indicator displayed “Changes Pending” when there were no updated settings to be published. This problem no longer occurs.
NGX-19930. The Identity Router Setup Console Network Diagnostics page no longer reports that the identity router failed to connect to two URLs used for software updates. The problem is corrected if you publish after the cloud or identity router upgrade is performed.
RSA SecurID Authenticate 2.0.1 for iOS is qualified with iOS 12 and contains bug fixes.
RSA SecurID Authenticate 2.0.1 for Android contains bug fixes.
The September 2018 release of the Cloud Authentication Service includes the following features and updates:
To enhance the security of device registration while minimizing user friction, this release introduces RSA SecurID Access My Page, a new web-based portal that uses multifactor authentication and QR or limited one-time-use numeric registration codes to complete device registration. See how this works.
If you are currently using the RSA SecurID Authenticate Device Registration access policy, be aware that the name and purpose of this policy will change in the September release to help control migration to My Page. The policy will be renamed to Device Registration Using Password and will allow you to control who can use password as the registration code. If necessary, update the policy configuration to align with your company needs.
Note that if you want to continue using a password to complete device registration, your users can enter their passwords as the registration code.
RSA SecurID Authenticate 2.0.0 for iOS, RSA SecurID Authenticate 2.0.0 for Android, and RSA SecurID Authenticate 3.0.0 for Windows 10 contain the following updates:
Updated device registration flow to work with RSA SecurID Access My Page. To register a device, iOS and Android users scan a QR code or enter a limited one-time-use numeric registration code. Windows 10 users enter a limited one-time-use numeric registration code.
Users only need to register a device if they are a new user, adding a new company, or switching a device. Existing users do not need to re-register.
If you require users to enter a PIN or Device Biometrics to view the Authenticate Tokencode, the process to reset a PIN has changed. iOS users will first be prompted for the device passcode. Android users will first be prompted for device credentials. Windows 10 users must first delete all the companies that protect the Authenticate Tokencode and then re-register those companies.
The RSA SecurID Authenticate for Android app is qualified with Android 9 Pie.
You can use the User Event Log API to export user audit logs from the Cloud Authentication Service. This feature improves auditing and security monitoring of end-user activity, which is useful for compliance audits, troubleshooting, risk assessment, and security information and event monitoring (SIEM) analysis. For more information, see RSA SecurID Access User Event Log API.
To further assist new customers in getting up an running more quickly, an additional preconfigured access policy has been added to the initial three delivered in August 2018. The fourth policy applies a context-driven criterion that uses the Identity Confidence attribute to determine if additional authentication is required. This fourth preconfigured access policy is only available to Premium edition customers.
Improved log messages for user synchronization events will make troubleshooting easier when users are automatically re-enabled or disabled in the Cloud Authentication Service, or when users are not found in the directory server during synchronization.
NGX-19192. In RADIUS and relying party deployments, the proxy server specified in the Identity Router Setup Console now handles traffic for authentication and product maintenance (such as cluster updates). In an SSO Agent deployment, the proxy server now handles traffic for product maintenance.
NGX-19829. Previously, you were unable to delete an identity source after you had visited the Clusters page. This problem has been fixed.
NGX-19798. In the Cloud Administration Console, the Device Enrollment policy is no longer included in the access policy count displayed on the Dashboard page. The Dashboard count includes your company’s custom access policies and preconfigured access policies.
RSA SecurID Authenticate 1.8.0 for iOS and RSA SecurID Authenticate 1.6.3 for Android contain bug fixes. For more information, see Critical Updates for RSA SecurID Access Components Used with the Cloud Authentication Service.
Users who need to complete device registration (for example, new users, users adding a new company in the app, or users switching devices) must update to these app versions before completing device registration.
Users who have already completed device registration are not required to update to these app versions. However, RSA recommends that users always use the latest version of the apps, so they have the latest fixes, features, and enhancements.
Critical Update for Identity Routers
The August 2018 release includes a critical fix for your identity router, which will be released Saturday, August 18, 2018. This critical update requires that you update your identity router software on or before August 29, 2018 to ensure continued connectivity to the service. For more information, click here.
What's New in This Release
This release also includes the following features and bug fixes:
New customers can get up and running more quickly using three preconfigured access policies that they can either use as is, or clone and customize. These customers do not need to create new access policies. For more information, click here.
You can generate and download a user report that displays your users’ Enable and Disabled status. This information improves visibility into your user population. For instructions, click here.
When you configure strong authentication to access the Cloud Administration Console, RSA SecurID Access prevents you from unintentionally locking yourself out by evaluating the access policy and verifying if it allows you to access the console. For example, the policy might exclude you based on identity source or contextual conditions. If you are excluded for any reason, you will be prevented from configuring this feature until you modify the policy or select a different policy. For configuration instructions, click here.
This release offers an optional sneak peek into a new direction that we are taking for RSA SecurID Authenticate device registration---including multifactor authentication and QR codes. If you want to try this new registration process, contact your RSA sales representative for more information.
The Cloud Authentication Service is now hosted on Microsoft Azure Australia Central, a protected-level Azure instance within the Canberra Data Centre. This new hosting option enables compliance with Australian and New Zealand Privacy Legislation. The data centers are designed for Australian government and critical infrastructure sectors.
NGX-19516. Previously, if a user was synchronized to the Cloud Authentication Service, deleted from a directory server, and then re-added using the same DN, the user could not be resynchronized to the Cloud Authentication Service. Now you can successfully resynchronize such users.
NGX-19643. When the Load Balancer DNS Name is not within the Protected Domain Name configured on the My Account > Company Settings page of the Cloud Administration Console, multiple identical event log messages are generated when a user attempts to sign out of the application portal. Now the Cloud Administration Console verifies if the Load Balancer DNS Name is within the Protected Domain Name, fixing the issue.
NGX-19737. Previously, under certain circumstances, users who entered their LDAP credentials correctly to access Microsoft Office 365 through a desktop client, and then expected to be prompted for additional authentication, instead encountered a script error that prevented them from authenticating. This problem has been fixed.
The Cloud Authentication Service includes the following features and bug fixes.
Disabled Users Automatically Changed to Pending Deletion
By default, the Cloud Authentication Service will automatically change the status of all Disabled users to Pending Deletion after the users have been disabled for 90 days, or the number of days you configure. Automatic bulk user deletion benefits your deployment by preventing inefficiencies that result from processing large numbers of disabled users.
Note: It is important to know that this feature takes effect immediately after the cloud upgrade goes live on July 21. At that time, the status of all users who have been Disabled for at least 90 days will automatically change to Pending Deletion, and these users will be automatically purged from the Cloud Authentication Service seven days after the upgrade. Purging removes all information and devices associated with the user from the Cloud Authentication Service. It does not remove users from the directory server. If any users were automatically marked Pending Deletion and you want to prevent them from being purged after seven days, click here for instructions.
Cloud Authentication Service Automatically Disables Users Missing From Directory Server
The Cloud Authentication Service now recognizes when previously synchronized users are either no longer present in the directory server or are excluded from the User Search Filter scope and disables these users in the Cloud Authentication Service during identity source synchronization. This feature ensures that users who may have been terminated from your organization can no longer authenticate. When automatic bulk user deletion is enabled, these users will automatically be changed to Pending Deletion after 90 days (or the number of days you configure), and then purged seven days after Pending Deletion.
Streamlined Authentication for RADIUS Users
The Cloud Authentication Service provides new features to deliver an optimized experience with reduced friction to RADIUS users:
You can configure RADIUS clients to send push notifications for Approve and Device Biometrics without forcing users to select an authentication method by entering a number, when one of these is the user's default method. Users who do not respond to the automatic notification within a configured timeframe can select any method provided from the assurance level in the access policy. The timeout does not apply if this feature is disabled and the user manually selects a method.
Some use cases require users to authenticate with LDAP passwords, but then RSA SecurID Access requires the same passwords a second time, before prompting for additional authentication. You can simplify authentication by configuring the RADIUS client to manage the primary authentication and the Cloud Authentication Service to only perform additional authentication, as determined by the access policy. When you enable this feature for a RADIUS client, users enter their passwords only once. See how this works.
Note: When this feature is enabled, either the RADIUS client must require password authentication, or the access policy must require all users to perform additional authentication. If you do not enforce either password or additional authentication, unauthorized users can gain access.
For complete information on RADIUS features, see RADIUS for the Cloud Authentication Service Overview.
If users enter a tokencode incorrectly or if a method times out before the user completes authentication, the user can choose to retry the same method. Previously, the method disappeared from the list of choices.
RSA SecurID Access Log Events API
To ensure audit log compliance with industry standards, the Cloud Authentication Service now supports a REST API to retrieve Administration logs from the service. For the complete list of events, click here.
The RSA SecurID Access Log Events API Software Developer Kit (SDK) contains a REST client command line tool that generates an Administration API access token and exports logs using the generated access token. To download the Software Development Kit, click here.
HTTPS Strict Transport Security (HSTS) for Standard and Custom Web Application Portals
HSTS forces compatible browsers to interact with the application portal and web applications using only the HTTPS protocol, which helps to protect these interactions against threats such as protocol downgrade attacks and cookie hijacking. It is enabled by default for standard and custom portals, but can be disabled on the Access > Portal Settings page of the Cloud Administration Console.
Updated Definitions for Identity Router Security Levels
The latest identity router version updates the encryption ciphers supported by the Medium and Low security levels for incoming connections, and adds the High security level, which allows only the most secure ciphers and encryption options.
Improved Visibility of NTP Service Synchronization
To assist with troubleshooting system issues, you can view NTP service synchronization status in two locations:
Identity Router Setup Console in Diagnostics > View Network Diagnostics
Identity Router Status Servlet in System Services
Improved Troubleshooting During Identity Router Setup
To more quickly identify network connection issues, when you connect an identity router to the Cloud Administration Console, the Identity Router Setup Console checks for connections to the Cloud Administration Console and Cloud Authentication Service that are required for authentication and product maintenance. If the identity router cannot connect to these URLs, the connection process is not successful and the Identity Router Setup Console lists the URLs to which it cannot connect.
Improved Look and Feel of RSA SecurID Authenticate Apps
RSA SecurID Authenticate 1.7.0 for iOS and RSA SecurID Authenticate 1.6.1 for Android contain the following updates:
Improved look and feel of the Approve authentication option
NGX-15746. Previously, when you changed the IP address of the identity router management or proxy interface using the VMWare Console, the address was not updated intermittently. This problem has been fixed.
NGX-17649. Previously, when you signed into the Cloud Administration Console, the publish status sometimes displayed a success message even if the last publish operation had failed. Now, when you sign in to the console, the publish status message is always accurate.
NGX-18622. When one or more identity providers are configured for automatic authentication on the Authentication Sources page of the Cloud Administration Console and a user cancels the first automatic identity provider authentication prompt that appears when attempting to access the application portal, the user is not automatically prompted to authenticate again during the same session. This is expected behavior.
NGX-18737. You no longer need to enter a value in the Portal Hostname field when adding an identity router to the Cloud Administration Console in order to set up an identity router.
NGX-18807. If you enter an invalid static route in the Identity Router Setup Console, a message indicates the static route is invalid.
NGX-19024. Previously, a time format mismatch caused failed connections and time and date errors when integrating the Cloud Authentication Service with RSA Authentication Manager if the Authentication Manager instance was deployed in certain time zones. This problem has been fixed.
NGX-19183. Communication issues that previously occurred between the identity routers due to DNS intermittency, connectivity, and timeout errors have been fixed.
NGX-19357. The identity source settings in the Cloud Administration Console and in the documentation have been updated to indicate more clearly that you must click the User Attributes tab and select the Synchronize the selected policy attributes with the Cloud Authentication Service checkbox. This setting ensures that user attributes are synchronized, which is required for additional authentication to succeed.
NGX-19497. Previously, when a user’s userPrincipalName (UPN) had a different suffix (@<domain>) than the user-joined domain, the user's IWA sign-in failed. This problem has been fixed.
NGX-19537. You can now reuse identity source names that were previously used for identity sources that have been deleted.
The Cloud Authentication Service includes the following features and bug fixes.
Microsoft AD FS Agents Provide Cloud-Based, Multifactor Authentication
The RSA Authentication Agent for Microsoft AD FS now supports cloud-based multifactor authentication methods such as Device Biometrics and push notifications by connecting your AD FS server and the Cloud Authentication Service.
Simplified Access Policy Wizard for Authentication Conditions
To improve ease of use, the Access Policy wizard has been simplified to reduce the number of steps necessary to configure authentication conditions.
Additional Condition Attributes for RSA SecurID Authenticate Device Registration Policy
To provide more control over which users can complete RSA SecurID Authenticate device registration, you can now use the Authentication Source, IP Address, and Trusted Network condition attributes in the RSA SecurID Authenticate Device Registration policy. For example, you might allow only users from certain IP addresses to complete device registration.
New System Event Monitor Improves Visibility
The System Event Monitor provides visibility into system-generated and managed events to aid in troubleshooting. You can filter the results according to Event Code, timeframe, and event type.
Restore Users Who Are Pending Deletion
You can use a bulk operation to undelete users who are Pending Deletion and restore them to their previous Disabled state. Disabled users can be re-enabled by the administrator or during synchronization. Undeleting prevents the users from being automatically purged from the Cloud Authentication Service. For example, this is useful if you deleted too many users from the Cloud and you want to restore those users.
RSA SecurID Authentication API Enhancements
The RSA SecurID Authentication API contains the following enhancements:
Initialize request supports specifying an assurance level outside of an access policy.
The keepAttempt parameter in the Initialize request applies to both completed and canceled authentication attempts.
The removeAttemptId parameter has been added to the Cancel request. The parameter requests to remove the authentication attempt ID as a part of this call.
NGX-19557. You can use the Delete Now button on the Users > Management page to immediately remove a user from the Cloud Authentication Service. This function is intended for emergency situations. For example, suppose you are trying to synchronize a record that has the same email address as a slightly different record for the same user that already exists in the Cloud Authentication Service. The user record fails to synchronize and the user cannot authenticate. You must delete the existing record from the Cloud Authentication Service and resynchronize in order to recreate the user record correctly so the user can complete authentication.
NGX-19521. Adding an identity router and saving a static DNS entry without an associated alias value no longer causes identity router registration to fail.
NGX-19074. Previously, under certain circumstances, you were unable to save an identity source after deleting one of the directory servers. This has now been fixed.
The Cloud Authentication Service includes the following features and bug fixes.
Approve Authentication Method Available with Device Unlock
You can now require users to unlock their devices before completing authentication using the Approve method. When this feature is enabled, users receive a notification on their registered devices, tap Approve, and are prompted to unlock their devices before authentication is completed.
Before enabling this option, instruct your users to update to the latest version of the RSA SecurID Authenticate app:
When this feature is enabled, after users update the app, the first time that they try to use Approve they must open the app, pull down to get the notification, and Approve from within the app. After the first use, Approve will work normally. Older app versions do not display a push notification and users must always open the app and pull down to respond to an Approve request.
Protected RSA SecurID Authenticate Device Registration
To help increase the security of end-user device registration, you can now use an access policy to control which users are allowed to complete device registration. You might want to use this access policy to allow only a subset of your users (for example, your Sales organization) to use the Authenticate app for additional authentication. When you enable the RSA SecurID Authenticate Device Registration policy you can specify identity source user attributes to define the target population for device registration. To learn more about this feature, click here.
Improved Management for User Deletion
You now have increased control when deleting a user from the Cloud Authentication Service. First, you mark the disabled user for deletion, which changes the user's account status to Pending Deletion. You can still view the user's detail information in the Cloud Authentication Service and synchronize a user who is Pending Deletion. After seven days, the user is automatically deleted from the Cloud Authentication Service. The user cannot register a device or authenticate to the Cloud Authentication Service while pending deletion or after deletion has taken place. Deletion removes all information and devices associated with the user from the Cloud Authentication Service.
You can also undelete a user who is pending deletion, which changes the user’s status from Pending Deletion to Disabled.
For instructions on deleting and undeleting users, click here.
LDAPv3 Account Status Now Synchronized with the Cloud Authentication Service
Users who have been disabled or expired in an LDAPv3 directory server are automatically disabled in the Cloud Authentication Service after manual, scheduled, or just-in-time synchronization. Disabled users cannot authenticate through the Cloud Authentication Service or register devices. You must manually map attributes for account status synchronization to happen. To learn more about identity source synchronization, click here and here.
Note: Make sure all LDAPv3 users who need to use the Cloud Authentication Service are active and enabled in the LDAPv3 directory server.
Additional Enhancements to User Account Synchronization
User account status in the Cloud Authentication Service is now more closely tied to the user account status in the Active Directory and LDAPv3 directory servers. The following enhancements were implemented:
Users who are disabled in any directory server and who do not have existing records in the Cloud Authentication Service are not added to the Cloud Authentication Service during synchronization.
Users who were re-enabled in the directory server or who are no longer expired, but are pending deletion in the Cloud Authentication Service, become re-enabled in the Cloud Authentication Service after synchronization.
Users who were manually disabled in the Cloud Authentication Service remain disabled and are not overridden during synchronization.
Simplified Planning and Setup Content
To help streamline the initial setup of your production deployment, the planning and setup content has been reorganized and simplified. The updated Planning Guide focuses on understanding the Cloud Authentication Service at a high level. Quick Setup Guides, available for each deployment type, walk you through both planning and setup. The guides are available here:
With these changes, the Solution Architecture Workbook and Setup and Configuration Guide are no longer available.
For custom security requirements, you can now specify the minimum PIN length if you require PIN or Device Biometrics to view the Authenticate Tokencode. The default PIN length is four. If users have registered the RSA SecurID Authenticate app with multiple companies, the PIN applies to the RSA SecurID Authenticate Tokencodes for all companies, and the minimum PIN length is the longest minimum PIN length of these companies.
To simplify user rollout, users can now complete RSA SecurID Authenticate device registration on devices that do not allow push notifications for the app. However, RSA recommends enabling or allowing push notifications for the RSA SecurID Authenticate options like Approve or Biometrics. This feature is useful in certain environments which have locked down push notifications, but want to use the RSA SecurID Authenticate Tokencode.
RSA SecurID Authenticate App iOS Upgrade
New minimum iOS operating system of version 10.0 for the RSA SecurID Authenticate for iOS app. Encourage your end users to upgrade to iOS version 10.0 or higher so they can continue using the app and take advantage of the latest improvements and bug fixes.
Incorrect Publish Status Message After the May Cloud Authentication Service Upgrade
After the Cloud Authentication Service is upgraded, the Changes Pending message appears in the Publish Status bar even if no changes are waiting to be published. You can safely ignore this message and it will disappear after your next publish operation.
NGX-19012. The User Event Monitor now reports errors for unsuccessful authentication attempts to SSO Agent applications when the identity router time and the Cloud Authentication Service time are out of synch.
NGX-19088. In the Cloud Administration Console, when you click My Account > Administrators to edit an administrator, in the API Configuration section, the examples provided for the IP Address and Netmask fields are now accurate and the fields are marked as required.
NGX-19066. Identity routers that are updated in debug mode no longer remain in the Updating phase.
NGX-19072. iOS and Windows users can now complete RSA SecurID Authenticate device registration if the Authenticate app or their devices do not receive push notifications.
NGX-19102. In the Cloud Administration Console, clearing the Enable the Identity Router REST API checkbox on the My Account > Administrators page correctly disables the API for an administrator.
NGX-19175. Unintentional audit logging changes are no longer saved to the Cloud Administration Console when Portal Settings are saved.
NGX-19176. RSA Support can now be enabled if a backup is added but not saved.
NGX-19177. Multiple audit log entries are no longer saved to the Cloud Administration Console if the backup schedule is changed and RSA Support is enabled.
NGX-19350. The Approve authentication method was failing intermittently to send notifications to Android mobile devices, resulting in failed authentications. This problem no longer occurs.
NGX-19397 and NGX-19431. Previously, when you edited and saved some existing SAML direct templates, extra attribute rows were created. This problem no longer occurs.
NGX-19494. If you are synchronizing identities from Active Directory Global Catalog, RSA recommends that you include accountExpires in the Partial Attribute Set to ensure that user accounts in the Cloud Authentication Service are enabled or disabled to match the directory server after synchronization. You no longer need to include the accountExpires attribute in the Partial Attribute Set to successfully synchronize the Cloud Authentication Service to an Active Directory Global Catalog.
The Cloud Authentication Service includes the following features and bug fixes.
Active Directory Account Status Now Synchronized with the Cloud Authentication Service
Users who have been disabled or expired in Active Directory are automatically disabled in the Cloud Authentication Service after manual, scheduled, or just-in-time synchronization. Disabled users cannot authenticate through the Cloud Authentication Service or register devices.
The next time you perform a publish operation and synchronize your Active Directory identity sources following the Cloud Authentication Service update on April 21, the Cloud Authentication Service will disable any cloud users whose accounts are already disabled or expired in Active Directory. This capability is not configurable. Support for LDAPv3 directory servers is expected in the near future.
Users who are disabled in Active Directory and who do not have existing records in the Cloud Authentication Service are not added to the Cloud Authentication Service during synchronization.
Note: Make sure all Active Directory users who need to use the Cloud Authentication Service are active and enabled in Active Directory.
Administrators Can Override User Account Status in the Cloud Authentication Service
You can use the Cloud Administration Console to manually enable and disable users. This feature applies to users from Active Directory and LDAPv3 directory servers. For information about user disablement and identity source synchronization, click here.
Enhanced Authentication Options Available in RSA SecurID Authenticate 2.0.1 for Windows
RSA SecurID Authenticate 2.0.1 for Windows adds support for the Approve and Biometrics options. As part of leveraging native biometric authentication capabilities, the Biometrics option supports any Windows Hello sign-in option.
Also, if you require additional authentication before viewing the Authenticate Tokencode, the tokencode can now be protected with an app-specific PIN, instead of Windows Hello. When a user tries to view the tokencode, the app prompts the user to create this PIN.
Users should update to this version when it is released.
SSO Agent Web Server User Traffic Uses Only https://
The Cloud Administration Console now ensures that all SSO Agent web server configurations use https:// for traffic between users and identity routers. You can no longer configure http:// for user traffic. You can still configure web servers to connect to backend application web servers over https:// or http:// as necessary. Also, the console has been improved to clarify steps for the SSO Agent web server configuration.
Identity Router Update Available
A new identity router update is now available with the following improvements:
Improved handling for environments with unreliable time synchronization.
Improved handling of out-of-memory conditions in cluster replication.
If you are using the SSO Agent, RSA recommends that you apply this update to your identity routers. If you have updated your identity routers after February 2018, your identity routers do not display OUT_OF_DATE, but you can update the cluster now using these instructions. If you do not take any action, these improvements are not applied to your identity routers until your next scheduled update.
NGX-17578. In the Cloud Administration Console, the Forgot Password popup has been improved to specify that the administrator must enter the same email address that belongs to Username.
NGX-18600. Single sign-on no longer fails if you accidentally add a leading or trailing space to an access policy name.
NGX-18889. IWA connector uses global catalog to search for users in the Active Directory forest and can now find a user based on the user's domain, even when multiple user records have the same sAMAccountName in the forest.
NGX-19037. When you search for a user by entering the user’s exact email address, the user, if found, appears at the top of the list.
NGX-19079. In the Cloud Administration Console, on the My Applications page, you are no longer prevented from editing an application if you added a SAML application before adding an identity source.
To see release notes that were published for earlier releases, see Release Notes Archive | Cloud Authentication Service and RSA SecurID Authenticate Apps.