Cloud Authentication Service Updates

The following sections provide information on the new and enhanced features of the Cloud Authentication Service (CAS).
  

CAS Now Supports OATH HOTP Hardware Authenticators

The Cloud Administration Console now allows administrators to view and manage OATH HOTP hardware authenticators. They can upload OATH HOTP OTP seed files to the Cloud Administration Console and assign authenticators to users. Consequently, users can self-register, activate, and manage their tokens on My Page.

Supported models are listed in the Cloud Administration Console when seeds are imported. For requesting support for additional HOTP models, administrators can contact RSA Technical Support.
  

New Identity Source Attribute – Manager

A new user identifier attribute, Manager, is now available in LDAP and Active Directory identity sources. In the Cloud Administration Console, administrators can configure and synchronize the Manager attribute for user accounts within LDAP and Active Directory identity sources. This attribute enables administrators to specify users' managers and identify to whom they report. In addition, the All Users report now includes a new column for the Manager attribute.
  

Enhanced Verbose Logging in the Cloud Administration Console

For more comprehensive logging, verbose logging now includes the Cloud portal Single Sign-On (SSO) related events, for example, user login events. Administrators can monitor user authentication events for applications and relying parties by selecting the Include Verbose Logs option on the User Event Monitor page.
  

Automatically Prefilled User ID Field on Login Authentication Page

When a user authenticates to a protected resource using FIDO, Emergency Access Code, or SecurID OTP authentication methods, their User ID is now stored on the login screen via a browser cookie. This enhancement ensures that the User ID input field is automatically pre-filled when a user attempts to log in again.
  

REMINDER: End of Support for RSA Authenticate App for iOS and Android

This is a reminder that the RSA Authenticate app for iOS and Android will soon reach its end of support, as communicated through previous advisories and the “Upcoming End of Primary Support (EOPS) Details” section below.

What Will Happen After March 31, 2024?

The RSA Authenticate app will remain functional, allowing existing users to continue authenticating. However, please note the following:

• RSA Authenticate app will no longer receive support and will not be qualified on future versions of iOS and Android OS.
• RSA Authenticate app will no longer be available for download from iOS and Android app stores.
• Starting from the April release of the RSA Cloud Authentication Service, users will be unable to register a newly installed RSA Authenticate app. Instead, they need to use the RSA Authenticator app.
• For any Cloud Authentication Service where the RSA Authenticate app was previously enabled:
  o RSA will automatically disable the use of the RSA Authenticate app.
  o RSA will automatically enable the use of the RSA Authenticator app.

Upcoming End of Primary Support (EOPS) Details

The following table provides details of the RSA products reaching the end of support within the next six months:

  
Third-Party Integrations from RSA Ready

The following integrations are recently completed or certified by RSA through the RSA Ready Technology Partner Program. Implementation Guides will be coming soon. For the complete catalog of Implementation Guides, see RSA Ready Integrations on the RSA Community.

• 1Password (new) – supports RSA Cloud Authentication Service using OIDC.
• Barracuda (update) – added support for the Authentication Manager using REST.
• ForgeRock Identity Cloud (new) – now supports RSA Cloud Authentication Service using SAML.
• Google Workspace (update) – added support for My Page SSO using SAML.
• Salesforce Slack (update) – added support for My Page SSO using SAML.