OAuth_problem=signature_invalid when trying to create an issue in Jira from my java application

Jorge Amat April 11, 2018

I'm getting the following error in Jira log when trying to create an issue from my java application:

2018-04-11 16:14:13,999 http-nio-8081-exec-8 WARN anonymous 974x1100x1 - 192.168.0.123 /rest/api/latest/issue [c.a.o.serviceprovider.internal.AuthenticatorImpl] Problem encountered authenticating OAuth client for url "http://example.com:8081/rest/api/latest/issue", error was "signature_invalid", with parameters "{oauth_problem=signature_invalid, oauth_signature=rKWSa6GEzeQOeddx1OeHXEIb7t3b4LBnoHrR1xxUpsD9mlSFx6JefEBGn/s5ZBOtM/w3kK+IEHVeeiBPl0LhaVIkmn2aJ01qkJvnByJ0nd9ryWCYZ3Sn8c6cah4ER0taUCN+HkL2L47NPMTC4jcn5HZGKm/phkljr5o3qNxcx5U=, oauth_signature_base_string=POST&http%3A%2F%2Fexample.com%3A8081%2Frest%2Fapi%2Flatest%2Fissue&oauth_consumer_key%3DOauthKey%26oauth_nonce%3D20243586694535%26oauth_signature_method%3DRSA-SHA1%26oauth_timestamp%3D1523456053%26oauth_token%3DDJgZkfen79tRrMJYKjphabVERQ6hj54Q%26oauth_version%3D1.0, oauth_signature_method=RSA-SHA1}

 

I could get read operations working well so my access token, public/private key and consumer key are well configured in both sides, however when trying "write operations" I'm getting always oauth_problem=signature_invalid.

I also removed proxy and ssl from jira instance to make sure this was not causing the problem, as per https://confluence.atlassian.com/applinks/oauth-troubleshooting-guide-790632058.html#OAuthtroubleshootingguide-OAuthinvalidsig

Regarding the other possibility pointed "The application URL for the link does not match the URL that the remote application is reporting.", my url is accesible from Jira server as I could reach it doing a curl (both Jira server and my app are in the same internal network).

Could you please help on this?

1 answer

0 votes
Amirul Ikhwan Omar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 17, 2018

This also can be caused  by 

  • The useBodyEncodingForURI tomcat parameter in the <jira-install>/conf/server.xml is set to true

If yes, you can change it to false.

Suggest an answer

Log in or Sign up to answer