> For the complete documentation index, see [llms.txt](https://docs.k9.io/key9-identity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.k9.io/key9-identity/web/marketplace/atlassian-jira.md).

# Atlassian Jira

**Atlassian required a subscription to Atlassian Guard Standard, to use SSO.**

[More information about Atlassian Guard can be found here.](https://support.atlassian.com/security-and-access-policies/docs/understand-atlassian-guard/)

To setup JIRA, we need two pieces of information.

1. **Service provider entity URL:** This url can be found in the SAML configuration via the Atlassian Admin.
2. **Service provider assertion consumer service URL**: This url can be found in the SAML configuration via the Atlassian Admin.

[Jira SSO setup information can be found here.](https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/)

Make sure you're an admin for an Atlassian organization.

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Navigate to: Security > Identity providers.
3. Select Set up SAML single sign-on.
4. Select **Other provider**, in the Identity Provider dropdown.
5. Enter **Key9** for the Directory name field
6. Add SAML details.

Copy and paste the URLs from your Atlassian organization to Key9 **Setup Items**

1. **Service provider entity URL**
2. **Service provider assertion consumer service URL**

After you have created your Key9 application, click the **SSO** tab in the side navigation, and copy the following information to Jira:

1. Copy the Key9 **Entity ID** url to the Identity provider Entity ID field.
2. Copy the Key9 **SSO** url to the Identity provider SSO URL.
3. Copy the Key9 **X.509 Certificate** to the Public x509 certificate field.

(To view and copy the x509 certificate in Key9, select **View Certificate Details** from the **Certificate Options** dropdown menu, then click the copy icon.)

**Save the SAML configuration and test the connection.**

\-------------------

By default, applications are not active upon creation. Active applications are immediately available to assign groups. Applications should only be activated when you have configured the Service Provider (SP).<br>