http status 404 on issue links and 400 on searches

[Cratesmith]

Hi, I just updated to obsidian 1.0.3 and latest version of this plugin and I'm getting this error instead of all links.

I'm currently authenticating via bearer token (it's a private jira server)

If I open the JiraIssue:Reuqest urls from the log in my browser they all work. Returning what seems to be the correct json, so I'm guessing this is an authentication issue with bearer token?

Interestingly when I hit "Test connection" the notification says it's working but the log shows a 401 error as the response. Which I suspect is where the real problem is happening.

I also tried basic authentication but that wouldn't connect.

[marc0l92]

I did not perform any tests on the bearer token because my company uses basic authentication method. Are you able to execute the requests performed by the plugin using a different client like curl or Postman?

[Cratesmith]

Yeah I can give it a shot tomorrow. For the time being I've manually rolled back to an older version which is working fine.

Sent with Proton Mail secure email.

------- Original Message ------- On Saturday, November 12th, 2022 at 6:29 AM, Marco Lucarella @.***> wrote:

I did not perform any tests on the bearer token because my company uses basic authentication method. Are you able to execute the requests performed by the plugin using a different client like curl or Postman?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[marc0l92]

An older version of this plugin? Are you able to tell me since wich version you have this issue?

[Cratesmith]

I'd have to step forward through each version, I'm not sure I had updated it each time. I suspect the error came in with the version that added multiple logins but I'd have to check to be sure.

Sent with Proton Mail secure email.

------- Original Message ------- On Saturday, November 12th, 2022 at 6:51 PM, Marco Lucarella @.***> wrote:

An older version of this plugin? Are you able to tell me since wich version you have this issue?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[JanLoehr]

Stumbled over this as well, then remembered I was working with Jira Bearer as well. You can just put in your username and the token as password in the basic auth settings. And it'll work. The API is a bit strange there.

[mathvdh]

Hi Everyone, first .. Thanks for this plugin ! I'm having the same issue as above, if I used Jira Cloud or Basic Authentication ... So when I enter my email AND api key in both and test the connection, it works. But when I link to an issue using JIRA:XXXXX or a link it gives the same error as OP

[mathvdh]

I'm a developer so please let know how I can help with this ?

[mathvdh]

Well I'm happy to add that it's now working somehow using Jira Cloud auth ... I don't know why ..

[mathvdh]

Of I figured it out, The reference to the ticket was missing a character, Sorry for the noise

[DNROO]

Hi All Thanks for creating this plug-in.

I am experiencing the same issue as the above getting the 404 Error. I am using the basic authentication and getting the test connection confirmed but am unable to get the jira issues running in the notes.Wwas there a fix for this?

[marc0l92]

The error 404 is displayed with the issue does not exists on the jira server configured. Your authentication is working if you get this error, but the issue BP-7435 does not exists.

[finoghentov]

@marc0l92 I experience the same problem.

JQL works 100% inside jira, also I successfully authenticated in system, because all inline issues work in this project.

Atlassian JIRA Project Management Software (v6.4.14#64029-sha1:ae256fe)

Maybe because of old version of jira?

UPD. Trying make raw curl and its work correctly.

curl -X GET -H "Content-Type: application/json" -d '{
  "jql": "project=KI", "fields": ["description"]
}' -u username:password myhost/rest/api/2/search