Go back to Jira and complete the configuration by inserting the following details: You’ll use it as the Client secret in Jira. In the left menu, select Certificates & secrets.Įnter a description and select an expiration date. Under Redirect URI, select Web and insert the URL from step 5. Under Supported account types, select Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. The work in Azure is outside of Jira’s support scope. Please reach out to your MSFT administrator or their documentation and support if you need additional assistance or have questions. The following are common high-level steps for setting up the OAuth 2.0 application and related parameters in Azure. Scopes - this is the level of the authenticated user data that you allow your service provider to share with the application. You will need the following data for the integration: Microsoft: Go to to learn how to generate the required data. Google: Go to to learn how to generate the required data. Go to the service provider to generate the data to enter on the plugin’s site to complete the integration.Make sure you provide an external URL (for example a load balancer for the Data Center). For example, Google does not allow it to be a private IP address. Copy the generated redirect URL, which you’ll have to provide at the service provider’s site to obtain the client ID and client secret.ĭifferent providers might have additional requirements related to the redirect URL.However, if you are using a custom service provider, you need to get this data from the service provider and fill it in yourself. For Google and Microsoft, we will auto-fill the authorization and the token endpoint data.Go to Jira administration > System > OAuth 2.0. Configure OAuth 2.0 for Google, Microsoft, or your own custom serverįor Detailed steps to configure OAuth 2.0 integration with Microsoft Azure check this KB. Next, you need to configure your mail server to use this integration. You first need to add OAuth 2.0 integration for your mail server to use. This is important as the redirect URL you’ll need to provide is based on Jira’s base URL. Your base URL needs to be configured correctly. If it doesn’t you will not be able to configure OAuth 2.0. Once you save your configuration, you can proceed to configure your mail server to use OAuth 2.0 as the authentication method. You need to provide the redirect URL that your application generated at the service provider’s site. Then, you need to copy the data to the OAuth plugin in your application to generate a redirect URL. You can generate this data on the service provider’s side. To do that you will require specific info such as a client ID from your service provider. You need to configure the OAuth 2.0 settings first. You need to be a system administrator to do that. You need to configure OAuth 2.0 for your Google and/or Microsoft email server and update your email server configuration. POP Support for OAuth 2.0 using Microsoft is only available for the following Jira versions:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |