raycast / extensions

Everything you need to extend Raycast.
https://developers.raycast.com
MIT License
5.39k stars 3.09k forks source link

[Jira Search (Self-Hosted)] ... #14349

Open mrkhachaturov opened 2 months ago

mrkhachaturov commented 2 months ago

Extension

https://www.raycast.com/emanguy/jira-search-self-hosted

Raycast Version

1.82.3

macOS Version

No response

Description

Extension always show error Check you network connection

Tested from local host with curl command

curl -H "Accept: application/json" \
     -H "Authorization: Bearer MDgwMTE4OTY2N.................." \
     "https://jira.example.net/rest/api/2/project"

Result shows all projects. So token is working and also there is no error with network.

Steps To Reproduce

1.defining jira server url and token

  1. unsafe https is disabled ( tried also with enabled, same result)

Current Behaviour

error Check you network connection

Expected Behaviour

Working extension

raycastbot commented 2 months ago

Thank you for opening this issue!

🔔 @emanguy @svenwiegand @koseduhemak @rnprest @LunaticMuch @nick318 @marinsokol you might want to have a look.

💡 Author and Contributors commands The author and contributors of `emanguy/jira-search-self-hosted` can trigger bot actions by commenting: - `@raycastbot close this issue` Closes the issue. - `@raycastbot close as not planned` Closes the issue as not planned. - `@raycastbot rename this issue to "Awesome new title"` Renames the issue. - `@raycastbot reopen this issue` Reopens the issue. - `@raycastbot assign me` Assigns yourself to the issue. - `@raycastbot good first issue` Adds the "Good first issue" label to the issue. - `@raycastbot keep this issue open` Make sure the issue won't go stale and will be kept open by the bot.
JeroenSchmidt commented 1 month ago

I have the same problem.

alexandru-borsevici-scopely commented 1 month ago

Same issue, it's a matter of changing authorizationHeader from jiraCredentials.ts Instead of Basic ${btoa(${email}:${token})}; Could be something like this: Bearer ${token};

Or give the option between personal token and basic authentication. And depending on config use proper authorizationHeader Kind regards,