8 Messages
Jira integration issue
Hi,
I’m working on Jira Service Desk Bidirectional Collibra Integration v1.0.3.
I believe integration is set up, but once I’m trying to trigger it via Postman (same for Curl), I’m getting bellow error:
{ “message”: “Internal error during execution.”,
“exceptionMessage”: “Content type ‘application/xml;charset=UTF-8’ not supported for bodyType=com.collibra.marketplace.jira.sd.model.jira.response.IssueTypeResponse”
}
Are you able to advise what should be changed/updated?
Regards,
Piotr
Community_Alex
683 Messages
•
15.3K Points
2 years ago
@spring-team.collibra.com Is this something you can help @collibra.advocate.7 with?
0
0
springboot_team
368 Messages
2 years ago
Hi @collibra.advocate.7,
This error is being thrown on the very first API call to Jira. We think the error is due to a 401 UNAUTHORIZED response from Jira API. This probably contains a non-JSON response , and since the integration is expecting a JSON response, this results in a “Content type not supported” error message (which is masking the 401 UNAUTHORIZED root cause error).
To confirm if our understanding is correct, can you please re-deploy the integration using DEBUG level logging?
If you deployed via the provided jar file, simply add “–debug” at the end of the java -jar command (i.e. java -jar sbi-jira-service-desk-1.0.3.jar --spring.config.location=/application.properties --debug).
Otherwise, if you are running the integration from the source code, simply change the log level of the “com.collibra” logger from INFO to DEBUG (line 33 in src/main/resources/log4j2.xml).
Our understanding will be correct if after the DEBUG log message “HTTP GET https://your-jira-host-name/rest/api/3/issuetype” you get the following log message : “Response 401 UNAUTHORIZED”. In case you get a different log message, can you please share it with us? You can share log messages with us via a private direct message if you do not wish to share this information publicly.
The cause of a 401 response could be either incorrect credentials in the jira connection properties (source.http.username and source.http.password) or, more probably, due to deprecation of basic authentication as explained here: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/.
If Basic Auth deprecation is causing this, then we would need to release a new version of the integration using a different authentication method.
Thanks,
@spring-team.collibra.com
1
0
piotrsa
8 Messages
2 years ago
hi Spring Boot Team,
yes, I’m using API token as user password.
Let me try add -debug and I will update you in private message.
Thank you.
Regards,
Piotr
1
borisahodikpe
11 Messages
1 year ago
Hi Team, @spring-team.collibra.com I’m having the same issue when trying to set up the connector. I’m using the Token key as password, even tried with Postman but I’m having the same error “Response 403 FORBIDDEN”.
The issue seems to be related only to the request type endpoint 2023-12-13 00:38:59,495 [scheduling-1] DEBUG org.springframework.web.reactive.function.client.ExchangeFunctions - [114d0e81] HTTP GET https://boristrial.atlassian.net/rest/api/3/issuetype
2023-12-13 00:38:59,677 [reactor-http-nio-6] DEBUG org.springframework.web.reactive.function.client.ExchangeFunctions - [114d0e81] [ff814ff4-1, L:/192.168.1.15:50461 - R:boristrial.atlassian.net/185.166.143.37:443] Response 200 OK
2023-12-13 00:38:59,679 [reactor-http-nio-6] DEBUG org.springframework.http.codec.json.Jackson2JsonDecoder - [114d0e81] [ff814ff4-1, L:/192.168.1.15:50461 - R:boristrial.atlassian.net/185.166.143.37:443] Decoded [{}]
2023-12-13 00:38:59,680 [scheduling-1] DEBUG org.springframework.web.reactive.function.client.ExchangeFunctions - [aef406d] HTTP GET https://boristrial.atlassian.net/rest/servicedeskapi/requesttype
2023-12-13 00:38:59,804 [reactor-http-nio-6] DEBUG org.springframework.web.reactive.function.client.ExchangeFunctions - [aef406d] [ff814ff4-2, L:/192.168.1.15:50461 - R:boristrial.atlassian.net/185.166.143.37:443] Response 403 FORBIDDEN
0
0