Certified: 1st February, 2022
Solution Summary
Use Case
When integrated, Atlassian Statuspage end users must authenticate with RSA SecurID Access to sign in. Atlassian Statuspage can integrate using SSO Agent and Relying Party.
Integration Types
SSO Agent integrations use SAML 2.0 technology to direct users’ web browsers to Cloud Authentication Service for authentication. SSO Agents also provide Single Sign-On to other applications using the RSA Application Portal.
Relying party integrations use SAML 2.0 to direct users’ web browsers to Cloud Authentication Service for authentication.
Supported Features
This section shows all of the supported features by integration type and by RSA SecurID Access component. Use this information to determine which integration type and which RSA SecurID Access component your deployment will use. The next section in this guide contains the steps to integrate RSA SecurID Access with Atlassian Statuspage for each integration type.
Atlassian Statuspage Integration with RSA Cloud Authentication Service
| Authentication Methods |
Authentication API |
RADIUS |
Relying Party |
SSO Agent SAML |
|---|---|---|---|---|
| RSA SecurID | - | - | ✔ | ✔ |
| LDAP Password | - | - | ✔ | ✔ |
| Authenticate Approve | - | - | ✔ | ✔ |
| Authenticate Tokencode | - | - | ✔ | ✔ |
| Device Biometrics | - | - | ✔ | ✔ |
| SMS Tokencode | - | - | ✔ | ✔ |
| Voice Tokencode | - | - | ✔ | ✔ |
| FIDO Token | n/a | n/a | ✔ | ✔ |
| Identity Assurance | - | - | ✔ | ✔ |
Atlassian Statuspage Integration with RSA Authentication Manager
| Authentication Methods |
Authentication API | RADIUS | Authentication Agent |
|---|---|---|---|
| RSA SecurID | - | - | - |
| On-Demand Authentication | - | - | - |
| Risk-Based Authentication | n/a | - | - |
| ✔ | Supported |
| - | Not supported |
| n/t | Not yet tested or documented, but may be possible. |
| n/a | Not applicable |
Configuration Summary
The following links provide instructions on how to integrate Atlassian Statuspage with RSA SecurID Access.
This document is not intended to suggest optimum installations or configurations. It assumes 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 in order to install the required components. All RSA SecurID Access and Atlassian Statuspage components must be installed and working prior to the integration.
Integration Configuration
Certification Details
Date of testing: 1st February, 2022
RSA Cloud Authentication Service
Atlassian Statuspage
Known Issues
No known issues
Related Articles
Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 718Number of Views Microsoft Entra ID External MFA - RSA Ready Implementation Guide 657Number of Views Palo Alto NGFW - RSA Ready Implementation Guide 411Number of Views Cisco ISE - RSA Ready Implementation Guide 360Number of Views Microsoft Entra ID - SCIM Client for Cloud Authentication Service - RSA Ready Implementation Guide 591Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide