When requesting a token using the java jiraClient
jira_home=https://macys-dev.atlassian.net/jira
getting a 404 and " Oops, you’ve found a dead link."
Is there something wrong with the URL I am using? The private_key I generated looks to be about half the size of the one that was in the config.properties that showed up initially.
The full stack trace is as follows:
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1070) at com.google.api.client.auth.oauth.AbstractOAuthGetToken.execute(AbstractOAuthGetToken.java:73) at com.atlassian.oauth.client.example.JiraOAuthClient.getAndAuthorizeTemporaryToken(JiraOAuthClient.java:37) at com.atlassian.oauth.client.example.OAuthClient.handleGetRequestTokenAction(OAuthClient.java:69) at com.atlassian.oauth.client.example.OAuthClient.execute(OAuthClient.java:51) at com.atlassian.oauth.client.example.ClientMain.main(ClientMain.java:18)
With the assumption that you’re working with Jira cloud, for your jira_home, can you try without the trailing /jira and see how it goes? I believe the trailing /jira is usually seen in server deployments.
I cannot post the client’s response from the server, it says “Sorry, new users can only put 2 links in a post.”
In short, it says
Feb 19, 2019 9:56:43 AM org.apache.http.impl.client.DefaultRequestDirector handleResponse
WARNING: Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm=“https%3A%2F%2Fmacys-dev.atlassian.net”, oauth_problem=“signature_invalid”
oauth_signature_method=RSA-SHA1
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1070)
at com.google.api.client.auth.oauth.AbstractOAuthGetToken.execute(AbstractOAuthGetToken.java:73)
at com.atlassian.oauth.client.example.JiraOAuthClient.getAndAuthorizeTemporaryToken(JiraOAuthClient.java:37)
at com.atlassian.oauth.client.example.OAuthClient.handleGetRequestTokenAction(OAuthClient.java:69)
at com.atlassian.oauth.client.example.OAuthClient.execute(OAuthClient.java:51)
at com.atlassian.oauth.client.example.ClientMain.main(ClientMain.java:18)
What was the exact request/command you did when you got this error? Were you able to get past the OAuth dance and was able to successfully request a token?
With this new error, I assume that the previous 404 was indeed caused by the incorrect jira_home.