Allow authentication to on-premise jira using personal access token

Question

robert-n-harris opened this issue 2 years ago · comments

Per my discussion with Cody on 10/26/2022, requesting added capability to authenticate to on-prem Jira instance with personal access token (PAT) as shown in https://github.com/andygrunwald/go-jira/blob/main/onpremise/examples/bearerauth/main.go#L15-L18

cbruno10 · Answer 1 · Thu Oct 27 2022 05:10:55 GMT+0800 (China Standard Time)

Thanks for raising an issue @robert-n-harris !

For anyone interested in adding this capability, here are some suggestions on where to get started:

Add new configuration arguments (personal_access_token) to support passing in a personal access token with support in https://github.com/turbot/steampipe-plugin-jira/blob/main/jira/connection_config.go
Update the connect function in https://github.com/turbot/steampipe-plugin-jira/blob/main/jira/utils.go#L16 to use this new config arg, based on the example in https://github.com/andygrunwald/go-jira/blob/main/onpremise/examples/bearerauth/main.go
- If token and personal_access_token, I'm not sure which one should take precedence, but for now token will be used if both are passed in, as Jira on-prem is deprecated and Jira Cloud is part of their main strategy moving forward.

Jean Francois Pambrun · Answer 2 · Fri Dec 23 2022 23:06:51 GMT+0800 (China Standard Time)

I was taking a look at the suggestion and it seems this would require migrating to the unreleased go-jira v2?

github-actions · Answer 3 · Wed Feb 22 2023 07:32:13 GMT+0800 (China Standard Time)

'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.'

github-actions · Answer 4 · Fri Mar 24 2023 07:32:21 GMT+0800 (China Standard Time)

'This issue was closed because it has been stalled for 90 days with no activity.'