Jira on prem - integration issue - API keys vs Personal access token

[florinmircea]

Hello,

  I'm unsuccessful in configuring the Jira integration ( On-prem instance ) in SecOps SOAR, receiving JiraError HTTP 403 url: .

  I believe the problem is related to API keys that the integration is expecting ( which works for Jira cloud ) versus  the PAT ( Personal access token ) that Jira on-prem offers by default .  I already checked the documentation https://cloud.google.com/chronicle/docs/soar/marketplace-integrations/jira , but there it mentions the API Key . As an example, Confluence integration has the PAT option ( https://cloud.google.com/chronicle/docs/soar/marketplace-integrations/atlassian-confluence-server ) . 

 Did someone managed to configure this Integration with Personal access token ? If not, are there any other ways of achieving this  out of the box ? ( Found online options with additional plugins , but I do not have admin access to Jira instance).

Thank you in advance.

[_K_O]

Hi @florinmircea, 

My team went through the Jira integration earlier this year. We created a service account for the integration and were able to use a remote agent to connect to the instance. 

For on-prem instances, you won't have the API key, but you can use the Username / Password combination for the connection which is why we opted for the Service Account instead of using an individual's credentials / PAT. 

"API Token, Note: This parameter can be used to contain the "Password" string in case of On-prem authentication, using username and password combination." 

• Reference: https://cloud.google.com/chronicle/docs/soar/marketplace-integrations/jira 

[florinmircea]

Hello @_K_O ,

 Thank you for the answer. I figured that much, unfortunately it is not easy to request such an account ( process wise ) , considering basic authentication is seen as less secure ( https://developer.atlassian.com/server/jira/platform/basic-authentication/ ) . Considering Confluence integration supports Personal Account Token, was hoping that there is a way ( maybe in the future ) to have this available for the Jira integration as well.