- #HOW TO ADD A USER ACCOUNT TO JIRA HOW TO#
- #HOW TO ADD A USER ACCOUNT TO JIRA UPDATE#
- #HOW TO ADD A USER ACCOUNT TO JIRA REGISTRATION#
- #HOW TO ADD A USER ACCOUNT TO JIRA PASSWORD#
Use this section to register and activate the JIRA app, and then assign users to the app.
#HOW TO ADD A USER ACCOUNT TO JIRA REGISTRATION#
Note: Use this account ID during JIRA registration in the "Registering and Activating the JIRA App" section.Ĭonfiguring the JIRA App in Oracle Identity Cloud Service Make a note of the account ID from the end of the SP Entity ID URL. On the SAML single sign-on page, under the Information required by your identity provider section, click copy near the SP Entity ID, and then make a note of the SP Entity ID URL.
#HOW TO ADD A USER ACCOUNT TO JIRA PASSWORD#
Note: Enabling SSO deactivates the ability to access JIRA using email address and password for domain verified users.
Paste the certificate content that you obtained earlier in the "Obtaining the Identity Provider Signing Certificate" section. See the "What Do You Need?" section.Įnter the Sign-in URL/SSO Endpoint: Public x509 certificate The Entity ID/Issuer URL information is located in the first line of the metadata. Use the metadata file that you downloaded earlier to obtain the Entity ID/Issuer URL.
#HOW TO ADD A USER ACCOUNT TO JIRA UPDATE#
Use the table to update the federated authentication attributes, and then click Save configuration. Under the Add SAML configuration section, click Add SAML configuration. In the left navigation menu, under ATLASSIAN ACCESS, click SAML single sign-on. In the left navigation menu, under ORGANIZATIONS & SECURITY, click Security. Note: Use this certificate content later during JIRA configuration in the "Configuring SSO for JIRA" section.Īccess JIRA as an administrator using the URL: The Invite new users page appears. This content is the Oracle Identity Cloud Service signing certificate.Īdd -BEGIN CERTIFICATE- at the beginning of the content.Īdd -END CERTIFICATE- at the end of the content. In the metadata file, locate the dsig:X509Certificate tags.Ĭopy the content between the dsig:X509Certificate tags into a text file. Use this section to obtain the Identity Provider Certificate in a format that is suitable for JIRA.Īccess the Identity Provider metadata file that you downloaded in the "What Do You Need?" section. Obtaining the Identity Provider Signing Certificate The same can be confirmed in the JIRA login URL: that you received in an email from Atlassian.
Use this file later to obtain the identity provider certificate content and during SSO configuration in JIRA in the "Obtaining the Identity Provider Signing Certificate" and "Configuring SSO for JIRA" sections respectively.Ī dedicated account name is required before you can register and activate the JIRA app.Īccount name is the value entered in the Claim your site field while creating an account with JIRA. You can use the following URL to access the metadata: and save the metadata in a text file. Make sure that the email ID of each user in JIRA matches the primary email ID of the Oracle Identity Cloud Service account.A JIRA account with a verified domain.An Oracle Identity Cloud Service account with authorization rights to manage apps and users (Identity Domain Administrator or Application Administrator).Admins can assign and revoke user access to the JIRA app using the Oracle Identity Cloud Service administration console.Users can start JIRA using the Oracle Identity Cloud Service My Apps console.Users can access JIRA using their Oracle Identity Cloud Service login credentials.It provides bug tracking, issue tracking, and project management functions.Īfter integrating JIRA with Oracle Identity Cloud Service: JIRA is a proprietary issue tracking product developed by Atlassian.
#HOW TO ADD A USER ACCOUNT TO JIRA HOW TO#
This document describes how to configure Oracle Identity Cloud Service to provide Single Sign-On (SSO) for JIRA using SAML.įor accessing the procedures in this document as a video, see Integrating JIRA with Oracle Identity Cloud Service. Previous Next JavaScript must be enabled to correctly display this content