Atlassian Jira - SAML Relying Party Configuration - RSA Ready Implementation Guide
Originally Published: 2022-02-09
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as Relying Party to Atlassian Jira.Procedure
- Sign in to RSA Cloud Administration Console.
- Click Authentication Clients > Relying Parties.
- On the Relying Party Catalog page, click Add a Relying Party and click Add for Service Provider SAML.
- On the Basic Information page, enter the name for the application in the Name field and click Next Step.
- On the Authentication page, choose SecurID manages all authentication.
- Select a Primary Authentication Method and Access Policy as required and click Next Step.
- Provide the Service Provider details in the following format:
- ACS URL: https://auth.atlassian.com/login/callback?connection=<saml.ID>
- Service Provider Entity ID: https://auth.atlassian.com/<saml.ID>
Refer to the Configure Atlassian Jira section to obtain the ACS URL and Entity ID.
- In the SAML Response Protection section, choose IdP signs assertion within response.
- Download the certificate by clicking Download Certificate.
- Click Show Advanced Configuration.
- Under the User Identity section, configure Identifier Type and Property. For example, Identifier Type: Auto Detect and Property: Auto Detect.
- Click Save and Finish.
- On the My Relying Parties page, click the Edit drop-down icon and select the Metadata option to download the metadata.
- Click Publish Changes. Your application is now enabled for SSO.
Configure Atlassian Jira
Perform these steps to configure Atlassian Jira.Prerequisites
Make sure that:
- You have Atlassian Access, which is an organization-level subscription that connects Atlassian cloud products to the Identity Provider.
- Your organization is registered and verified in Atlassian Access.
- Atlassian Jira is configured in Atlassian Access.
- Log on to http://admin.atlassian.com/.
- Select your organization > Security > Identity Providers.
- Click Choose in the Other provider section.
- Provide a name for the Identity Provider and click Add.
- Provide the following details and click Next.
- Identity Provider Entity ID – The EntityID value that can be obtained from the metadata file downloaded from RSA.
- Identity Provider SSO URL – The SingleSignOnService value that can be obtained from the metadata file downloaded from RSA.
- X509 Certificate – Upload the certificate that was downloaded from RSA.
- Copy the Service Provider Entity URL and ACS URL and click Next.
- Select your Domain and click Next.
- Click Stop and save SAML.
Return to Atlassian Jira - RSA Ready Implementation Guide.
Related Articles
Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 110Number of Views Workday - SAML Relying Party Configuration - RSA Ready Implementation Guide 4Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 252Number of Views Microsoft Entra ID - SAML Relying Party Configuration - RSA Ready Implementation Guide 87Number of Views Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 527Number of Views
Trending Articles
AFX Server remains in a 'Not running' State, afx status shows 'timed out waiting for AFX applications to start' and mule_e… Downloading RSA Authentication Manager license files or RSA Software token seed records RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.7 SP1 Patch 1 Hotfix 1 RESTful Web Service Connector capability test fails with unauthorized (401) error when using Basic authentication in RSA G…
Don't see what you're looking for?