# Jira and Confluence connector issue **URL:** \ **Category:** Elastic Search\ **Created:** [September 19, 2022, 10:42am UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684 "2022-09-19T10:42:40Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![PA3mEP](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@PA3mEP](https://discuss.elastic.co/u/PA3mEP)\ **Post date:** [September 19, 2022, 10:42am UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/1 "2022-09-19T10:42:40Z")
Hi, beautiful people. It seems that I cannot integrate out Jira and Confluence with Enterprise Search any more. Jira(Server) version 9.0.0 and Confluence(Server) 7.18.2. It feels like Atlassian has deprecated OAuth1.0 and now using OAuth2.0 only. Am I correct? Any plans on updating Atlassian connectors? PS. If I'm wrong, then can you point me to a appropriate documentation page? ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [September 19, 2022, 1:14pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/2 "2022-09-19T13:14:03Z")
Hi @PA3mEP , What version of Enterprise Search are you using? There was a bug in 8.3.x where Confluence Server and Jira Server could not be appropriately configured for OAuth 1.0, but that is fixed in 8.4.x. Could that be your issue? ---
**Author:** ![PA3mEP](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@PA3mEP](https://discuss.elastic.co/u/PA3mEP)\ **Post date:** [September 20, 2022, 7:46am UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/3 "2022-09-20T07:46:32Z")
Just 2 weeks ago upgraded my Elasticstack(Elasticsearch, Kibana, Logstashes, Beats etc.) to version 8.4.1. ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [September 20, 2022, 6:13pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/4 "2022-09-20T18:13:38Z")
Hmm interesting. Ok, can you explain more about the issue you're having, and where you're noticing the disconnect? We have never tested against Jira Server 9.x. I'm not confident if that will work, but am also not sure that it wouldn't. We also haven't tested against Confluence Server 7.18.x, but we have tested against 7.13.x, and I wouldn't think Atlassian would make a breaking change in a minor version upgrade. ---
**Author:** ![PA3mEP](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@PA3mEP](https://discuss.elastic.co/u/PA3mEP)\ **Post date:** [September 21, 2022, 10:07am UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/5 "2022-09-21T10:07:17Z")
Well, I'm facing this issue during the configuration of Application Link between Enterprise search and Jira for example. From Enterprise Search side. Configuration parameters are looking as follows ![Enterprise Search Config](https://us1.discourse-cdn.com/elastic/original/3X/4/a/4ad46f99a11c4ae0addfce5542cf40446db6a144.png) So Enterprise Search gives me 2 parameters "Public Key" and Customer Key. OK, that's nice. Now in Jira Application Link configuration looks as follows ![Jira 1](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e8e4b2a2bb4d65ff2993e50005c5077d71a1d393.png) In this case I assume that it must be a Incoming Application Link Next step in wizard looks as follows ![Jira 2](https://us1.discourse-cdn.com/elastic/original/3X/c/a/ca651fea4f46d6967369c15148b78e5f85b1617d.png) Where redirect URL is URL of Enterprise search, I think. And on a final step ![Jira 3](https://us1.discourse-cdn.com/elastic/original/3X/9/2/920043343c6f2fa220d591f06a0bfcb64c1daf1f.png) Jira gives me Client ID and secret. Which is weird, what do I do with them? And ok, Let's assume that it must be Outgoing type of Application Link. Then Configuration dialog looks as follows ![Jira Outgoing](https://us1.discourse-cdn.com/elastic/original/3X/b/3/b306bcea96a48e525be930d24e561bd71dcbd23a.png) Here I don't understand where to get these parameters like ClientID, ClientSecret etc. ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [September 21, 2022, 4:20pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/6 "2022-09-21T16:20:47Z")
Thanks @PA3mEP , this is helpful. I was able to find that Jira Server 8.22 is where they added support for OAuth2 Application Links: [Jira Software 8.22.x release notes | Atlassian Support | Atlassian Documentation](https://confluence.atlassian.com/jirasoftware/jira-software-8-22-x-release-notes-1115656979.html) However, I wasn't able to find any release notes saying that they removed support for OAuth1, and reading the current docs here: [Link to other applications | Administering Jira applications Data Center and Server 9.2 | Atlassian Documentation](https://confluence.atlassian.com/adminjiraserver/link-to-other-applications-938846918.html) It seems that they have put OAuth1 under **Atlassian product** as the link type. Can you give that a try? ---
**Author:** ![PA3mEP](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@PA3mEP](https://discuss.elastic.co/u/PA3mEP)\ **Post date:** [September 21, 2022, 6:47pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/7 "2022-09-21T18:47:17Z")
Maaan, you are a genius. That was it. Hell, Atlassian, what were they thinking? First of all indeed you have to select Atlassian Product, but then you provide an URL of Enterprise search and then Wizard MUST fail, and then it will show that old style from where you can configure OAUTH1 Application link. Cheeeezzz. Thanks, man, I appreciate the help. I wish I was that smart... 🤣 ---
**Author:** ![PA3mEP](https://avatars.discourse-cdn.com/v4/letter/p/53a042/32.png) [@PA3mEP](https://discuss.elastic.co/u/PA3mEP)\ **Post date:** [September 21, 2022, 6:54pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/8 "2022-09-21T18:54:32Z")
Yeah, wanted to add few things. 1. About that form in the Application Link configuration where you paste URL of Enterprise Search. That form MUST fail twice, and only then it will show the form we are looking for. 2. Same goes for Confluence as well. Got my Application Links configured and working perfectly 👍 ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [September 21, 2022, 7:01pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/9 "2022-09-21T19:01:21Z")
Glad to hear it! Don't hesitate to submit support or community posts to Atlassian to share feedback to them that you have on this flow. I'll make a note that we may want to update our docs so that the next person doesn't have to guess at this flow with the newer versions of Atlassian's "Server" projects. There's very little chance that Workplace Search will be updated to work with the OAuth2 flows of Atlassian's "Server" projects, as they are trying to phase out those server products, so it's probably not worth our investment. Thanks again for raising this, and I'm glad you got it working! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 19, 2022, 7:02pm UTC](https://discuss.elastic.co/t/jira-and-confluence-connector-issue/314684/10 "2022-10-19T19:02:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.