Fortra GoAnywhere - RSA Ready Implementation Guide
10 months ago

Certified: 02/19/2025 

Solution Summary

This article describes the configuration steps involved in integrating Fortra GoAnywhere with RSA Cloud Authentication service using SAML 2.0.

 

Integration Types

This article describes the configuration steps involved in integrating Fortra GoAnywhere with RSA Cloud Authentication service using SAML 2.0.

My Page SSO provides Single-Sign-On (SSO) to Fortra GoAnywhere users leveraging RSA self-service portal My Page. When integrated, users must authenticate with RSA to sign in Fortra GoAnywhere. SP-initiated SSO is supported. Modern Cloud-hosted SSO with My Page replaces the existing SAML SSO support with the IDR. Existing SSO integrations using IDR My Applications continue to be supported and will be listed in this document as applicable.

Note: RSA will continue to maintain existing SAML SSO integrations using IDR My Applications. At a to-be-determined future date, RSA will announce the end-of-life (EOL) date for the SAML SSO support with the IDR. For more information Available Now: My Page SSO Enhancements - RSA Community - 680715

Relying Party integration allows Fortra GoAnywhere users’ web browsers to be automatically redirected to RSA Cloud Authentication Service for authentication. With Relying Party integration, Cloud Authentication Service can manage only additional authentication or both primary authentication (for example, user ID and password) and additional authentication.

Supported Features

This section shows when integrated with RSA Cloud Authentication Service using SAML 2.0, GoAnywhere users can authenticate with any of the following multi-factor authentications.

 

 Fortra GoAnywhere Integration with RSA Cloud Authentication Service

Authentication Methods

Relying Party

My Page SSO

Approve
Authenticate OTP 
Device Biometrics
SMS OTP
Voice OTP
SecurID OTP
LDAP Password
FIDO Token
QR Code
Emergency Access Code

 

 Fortra GoAnywhere Integration with RSA Authentication Manager

Authentication Methods

Authentication API

RADIUS

Authentication Agent

RSA SecurID---
On-Demand Authentication---
Risk-Based Authenticationn/a--

 

Supported
-Not supported
n/tNot yet tested or documented, but may be possible.

Configuration Summary

The following links provide instructions on how to integrate GoAnywhere with RSA Cloud Authentication Service using all supported integration types. This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products to install the required components. 

All RSA and GoAnywhere components must be installed and working prior to the integration. 

 

Integration Configuration

 

RSA Terminology Changes

The following table describes the differences in the terminologies used in the different versions of RSA products and components. 

Previous Version

New Version

Examples/Comments

Company IDOrganization ID 
AccountCredential 
TokenOTP Credential

SecurID OTP Credential

TokencodeOTP/Access Code

SecurID OTP, SMS OTP, Voice OTP

Emergency Access Code, Disable Access Code

Hardware TokenHardware Authenticator 
Device Serial NumberBinding ID 
DeviceCredential/Authenticator 
Device Registration CodeRegistration Code 
Authenticate AppAuthenticator App 

 

Certification Details

RSA Cloud Authentication Service

GoAnywhere

Windows Server 2019

 

Known Issues

No known issues.