# Cannot connect to JIRA Cloud due to ':' in account id

**URL:** <https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837>\
**Category:** Elastic Search\
**Tags:** connectors\
**Created:** [June 5, 2024, 9:00am UTC](https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837 "2024-06-05T09:00:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hunsw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hunsw/32/93637_2.png) [@hunsw](https://discuss.elastic.co/u/hunsw)\
**Post date:** [June 5, 2024, 9:00am UTC](https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837/1 "2024-06-05T09:00:40Z")

</div>

I'm trying to connect to JIRA Cloud with the Elasticsearch Connector, but the attempt fails since my cloud id contains a colon (':').

The error message I get references the relevant RFC:\

[FMWK][08:57:58][ERROR] [Connector id: xxxxx, index name: mycompany-jira, Sync job id: xxxxxxxx] A ":" is not allowed in login (RFC 1945#section-11.1)

I've tried everything like omitting the colon, escaping it, urldecoding it, nothing works.

It'd be very important for our Enterprise project...

---

<div class="post-metadata">

**Author:** ![Artem\_Shelkovnikov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_shelkovnikov/32/134322_2.png) [@Artem\_Shelkovnikov](https://discuss.elastic.co/u/Artem_Shelkovnikov)\
**Post date:** [June 5, 2024, 9:23am UTC](https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837/2 "2024-06-05T09:23:19Z")

</div>

Theoretically url encoding it (replacing `:` with `%3A`) should work.

Do you receive different message when you do it?

Additionally, it really looks like a bug in the connector - it will help us prioritise and fix it if you submit a bug ticket [here](https://github.com/elastic/connectors/issues/new?assignees=&labels=bug&projects=&template=bug_report.md&title=).

---

<div class="post-metadata">

**Author:** ![hunsw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hunsw/32/93637_2.png) [@hunsw](https://discuss.elastic.co/u/hunsw)\
**Post date:** [June 5, 2024, 9:27am UTC](https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837/3 "2024-06-05T09:27:23Z")

</div>

Unfortunately even though url decoding makes the id RFC-compliant, but results in a 401 - unauthorized error.

---

<div class="post-metadata">

**Author:** ![hunsw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hunsw/32/93637_2.png) [@hunsw](https://discuss.elastic.co/u/hunsw)\
**Post date:** [June 5, 2024, 10:07am UTC](https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837/4 "2024-06-05T10:07:41Z")

</div>

After inspecting the code it turned out that the admin email account had to be entered as Jira Cloud service account id. (So something like [admin@example.com](mailto:admin@example.com) and not the Cloud ID.)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 3, 2024, 10:08am UTC](https://discuss.elastic.co/t/cannot-connect-to-jira-cloud-due-to-in-account-id/360837/5 "2024-07-03T10:08:13Z")

</div>

Closed on July 3, 2024, 10:08am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.