Opening JIRA issue with personal_access_token does not work

[vszakd]

Hello, we tried opening an issue using master with a PAT but we get:

returned status 403 Forbidden, error "request failed. Please analyze the request body for more details. Status code: 403", body """}

If we copy/paste the URL after "JIRA request ..." in the browser in an authenticated session in the browser it works correctly (the URL requests existing issues).

Thanks.

[sfh-darknet]

We are having the same issue. Exact same issue/error as @vszakd

[sfh-darknet]

@vszakd I got it working by using the helm chart and specifying the username and token.

config: template: jiralert.tmpl defaults: # API access fields. api_url: "https://REDACTED.atlassian.net" user: 'atlassian.robot@REDACTED' password: 'REDACTED'

[vszakd]

Great @sfh-darknet, what version are you using inside the chart? What did you put in place of REDACTED?

On Fri, 6 Oct 2023 at 12:08, sfh-darknet @.***> wrote:

@vszakd https://github.com/vszakd I got it working by using the helm chart and specifying the username and token.

config: template: jiralert.tmpl defaults: # API access fields. api_url: " https://REDACTED.atlassian.net" user: @.***' password: 'REDACTED'

— Reply to this email directly, view it on GitHub https://github.com/prometheus-community/jiralert/issues/177#issuecomment-1750335145, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACA2RWR4CJP5O4HQCS6DAI3X57KBLAVCNFSM6AAAAAA5MT277GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQGMZTKMJUGU . You are receiving this because you were mentioned.Message ID: @.***>

[sfh-darknet]

Just the latest, for password I put my token :) @vszakd