Certified: 1st February, 2022

Solution Summary

Use Case

When integrated, Atlassian Opsgenie end users must authenticate with RSA SecurID Access to sign in. Atlassian Opsgenie 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 Opsgenie for each integration type.

Atlassian Opsgenie Integration with RSA Cloud Authentication Service

Atlassian Opsgenie Integration with RSA Authentication Manager

Configuration Summary

The following links provide instructions on how to integrate Atlassian Opsgenie 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 Opsgenie components must be installed and working prior to the integration.

Integration Configuration

• SAML Relying Party
• SAML SSO Agent

Certification Details

Date of testing: 1st February, 2022

RSA Cloud Authentication Service

Atlassian Opsgenie

Known Issues

No known issues.