How to integrate Cisco FMC with the SecurID Cloud Authentication Service SSO Portal
Originally Published: 2022-07-29
Article Number
Applies To
- RSA Product set: SecurID Access
- RSA Product/Service Type: Cloud Authentication Service
- RSA Version/Condition: any
- Cisco Firepower Management Center (FMC), Version 7.0.x
Issue
Cisco provides its own Firepower Management Center Configuration Guide, Version 7.0, with a section to Configure Single Sign-On with Any SAML 2.0-Compliant SSO Provider .
This KB articles provides the necessary additional information needed when following that guide to successfully configure the SecurID Cloud Authentication Service as the Identity Provider (IdP) for Cisco FMC.
Tasks
For this integration, bear in mind that the Cisco side will be the SAML Service Provider (SP) and the SecurID side will be the SAML Identity Provider (IdP) and Issuer.
Follow the Cisco Configure Single Sign-On with Any SAML 2.0-Compliant SSO Provider instructions (referred to as "the Cisco guide" below) to determine what must be configured. However, Cisco has the following two requirements in addition to what is mentioned in that guide:
- The SAML Issuer Entity Identifier must be in URL format
- The SAMLresponse sent to Cisco FMC must include the SAML RelayState parameter with an unencoded value of /ui/logon
When configuring the SAML application in the Cloud Administration Console:
- Use the SAML Direct template
- Select IDP-initiated
- If you are creating an IDR SAML Application, set Connection URL to/ui/logon
- Set the Assertion Consumer Service (ACS) URL to the value specified in the Cisco guide for "Single Sign on URL, Recipient URL, Assertion Consumer Service URL"
- Set the Audience (Service Provider Entity ID) to the value specified in the Cisco guide for "Service Provider Entity ID, Service Provider Identifier, Audience URI"
- If you are creating a Cloud SAML Application, click to expand Show IdP Advanced Configuration
- For the Identity Provider Entity ID, choose the Override option, and set any valid URL as the Identity Provider Entity ID. We suggest just copying the entire Identity Provider URL value and using it as the Identity Provider Entity ID (which would mean Identity Provider Entity ID and Identity Provider URL would both have the same value).
- Click to expand Advanced Configuration or Show Connection Profile Advanced Configuration
- For User Identity, the Identifier Type must be Email Address and the chosen Property must be in email address format for all users.
- If you are creating an IDR SAML Application, in section Uncommon Formatting SAML Response Options, subsection Relay State URL Encoding, uncheck Send encoded URL in outgoing assertion and make sure all other options there are unchecked.
- If you are creating a Cloud SAML Application, set Relay State to/ui/logon
Resolution
Notes
- The SAML Response Signature certificate (IDR SSO) or SAML Response Protection certificate (Cloud SSO) in the SAML Application in the Cloud Administration Console is what the Cisco guide refers to as just "X.509 Certificate".
- If RelayState is not configured but everything else is configured correctly, a successful authentication will result in Cisco FMC displaying the error 404 Page note found.
Related Articles
Integrate Ozeki SMS Gateway with RSA Authentication Manager 8.x 42Number of Views How to integrate SWIFT Alliance Access with RSA Authentication Manager using RADIUS protocol 102Number of Views Integrating RSA Authentication Agent with RSA Authentication Manager 8.1 Risk-Based Authentication 8Number of Views Integrate Citrix NetScaler with RSA Authentication Manager 8.x 178Number of Views OIDC: How to integrate applications with the RSA Cloud Authentication Service 324Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Downloading RSA Authentication Manager license files or RSA Software token seed records
Don't see what you're looking for?