OPSWAT MetaDefender Core - RSA Ready Implementation Guide
Last Modified: 2024-08-27
Solution Summary
This guide describes OPSWAT MetaDefender Core integration with RSA ID Plus using SAML 2.0. Use this information to determine which use case and integration type your deployment will employ.Use Case
OPSWAT MetaDefender Core can be integrated with RSA using My Page SSO. When integrated, users must authenticate with RSA to sign in to OPSWAT MetaDefender Core.
Integration Types
My Page SSO provides Single-Sign-On (SSO) to OPSWAT MetaDefender Core users' leveraging RSA self-service portal My Page. IdP-initiated SSO is supported.Modern Cloud-hosted SSO with My Page replaces the existing SAML SSO support with the IDR.
Supported Features
This section shows all the supported features by integration type and by RSA components. Use this information to determine which integration type and RSA component your deployment will use. The next section in this guide contains the instruction steps for how to integrate RSA with OPSWAT MetaDefender Core using each integration type.OPSWAT MetaDefender Core Integration with RSA Cloud Authentication Service
| Authentication Methods | RSA MFA API (REST) | RADIUS | Relying Party | My Page SSO |
| Approve | - | - | - | |
| LDAP Password | - | - | - | |
| SecurID OTP | - | - | - | |
| Authenticate OTP | - | - | - | |
| Device Biometrics | - | - | - | |
| SMS OTP | - | - | - | |
| Voice OTP | - | - | - | |
| FIDO Security Key | - | - | - | |
| QR Code | - | - | - | |
| Emergency Access Code | - | - | - | |
OPSWAT MetaDefender Core Integration with RSA Authentication Manager
| Authentication Methods | RSA MFA API (REST) | RADIUS | Authentication Agent |
|---|---|---|---|
| RSA SecurID | - | - | - |
| On Demand Authentication | - | - | - |
| Risk-Based Authentication | - | - | - |
| Supported | |
| - | Not supported |
| n/t | Not yet tested or documented, but may be possible |
| n/a | Not applicable |
Configuration Summary
This section contains instruction steps that show how to integrate OPSWAT MetaDefender Core with RSA using all of the 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 OPSWAT MetaDefender Core components must be installed and working prior to the integration.
Integration Configuration
RSA Cloud Authentication Service
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 ID | Organization ID | |
| Account | Credential | |
| Token | OTP Credential | SecurID OTP Credential |
| Tokencode | OTP/Access Code | SecurID OTP, SMS OTP, Voice OTP Emergency Access Code, Disable Access Code |
| Hardware Token | Hardware Authenticator | |
| Device Serial Number | Binding ID | |
| Device | Credential/Authenticator | |
| Device Registration Code | Registration Code | |
| Authenticate App | Authenticator App |
Certification Details
RSA Cloud Authentication ServiceOPSWAT MetaDefender Core
Known Issues
IdP-initiated SSO flow is supported. However, the SP-initiated SSO flow will not work due to the following issue:According to SAML standards, for the SP-initiated SAML SSO flow to work successfully, the Assertion Consumer Service (ACS) URL configured in the RSA platform (Identity Provider) and the SAML request generated by the MetaDefender Core (Service Provider) must contain “<AssertionConsumerServiceURL>” tag with the exact same ACS URL configured in the RSA platform.
SAML validation involves cross-verifying the configured ACS URL and Entity ID with the received ACS URL & Entity ID from the SAML request.
In this case, the SAML request generated by the MetaDefender Core does not include “<AssertionConsumerServiceURL>” tag. Instead, it contains an “<AssertionConsumerServiceIndex>” tag, which causes RSA to throws an “Invalid Request” error.
