com.atlassian.sal.api.net.ResponseException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Copied to https://ecosystem.atlassian.net/browse/APL-992 We have noticed a behaviour where two applications located across different time zones with applinks connecting them have a weird situation where resource sharing fails with the error below: {noformat} 012-06-19 14:49:52,318 http-8443-36 WARN anonymous 889x58167x1 - 63.246.18.90,127.0.0.1 /plugins/servlet/oauth/request-token [serviceprovider.internal.servlet.RequestTokenServlet] Rejecting OAuth request for url "https://jira.sultan.com/plugins/servlet/oauth/request-token" due to invalid timestamp ({oauth_problem=timestamp_refused, oauth_acceptable_timestamps=1340109892318-1340110492318}). This is most likely due to our system clock not being synchronized with the consumer's clock. 2012-06-19 14:50:39,559 http-8443-30 WARN alexandre.alquier@sultan.com 890x58179x1 pocngl 82.127.114.234,127.0.0.1 /plugins/servlet/applinks/oauth/login-dance/authorize [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", oauth_problem="consumer_key_unknown"} 2012-06-19 14:50:39,559 http-8443-30 ERROR alexandre.alquier@sultan.com 890x58179x1 pocngl 82.127.114.234,127.0.0.1 /plugins/servlet/applinks/oauth/login-dance/authorize [core.auth.oauth.OAuthApplinksServlet] An error occurred when performing the oauth 'dance' for application link 'sultan (d138ac5b-109f-389b-a6fd-ed6acf8b5a80) https://sultan.onconfluence.com com.atlassian.applinks.application.confluence.ConfluenceApplicationTypeImpl@7db75f15' com.atlassian.sal.api.net.ResponseException: Failed to get token from service provider, problem was: 'consumer_key_unknown', full details: OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", oauth_problem="consumer_key_unknown" at com.atlassian.applinks.core.auth.oauth.OAuthTokenRetriever$1.handle(OAuthTokenRetriever.java:118) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$1.handle(JerseyRequest.java:142) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$1.handle(JerseyRequest.java:139) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:163) at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:307) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:158) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.execute(JerseyRequest.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.module.ContextClassLoaderSwitchingProxy.invoke(ContextClassLoaderSwitchingProxy.java:27) at $Proxy1365.execute(Unknown Source) {noformat} Common features effected by this issue is gadget subscription between JIRA and the other application such as confluence. *Workaround* Modify the timezones to match as per our [Setting the timezone for the JAVA environment|https://confluence.atlassian.com/display/JIRAKB/Setting+the+timezone+for+the+JAVA+environment] KB.
    via by Sultan Maiyaki [Atlassian],
  • Copied to https://ecosystem.atlassian.net/browse/APL-992 We have noticed a behaviour where two applications located across different time zones with applinks connecting them have a weird situation where resource sharing fails with the error below: {noformat} 012-06-19 14:49:52,318 http-8443-36 WARN anonymous 889x58167x1 - 63.246.18.90,127.0.0.1 /plugins/servlet/oauth/request-token [serviceprovider.internal.servlet.RequestTokenServlet] Rejecting OAuth request for url "https://jira.sultan.com/plugins/servlet/oauth/request-token" due to invalid timestamp ({oauth_problem=timestamp_refused, oauth_acceptable_timestamps=1340109892318-1340110492318}). This is most likely due to our system clock not being synchronized with the consumer's clock. 2012-06-19 14:50:39,559 http-8443-30 WARN alexandre.alquier@sultan.com 890x58179x1 pocngl 82.127.114.234,127.0.0.1 /plugins/servlet/applinks/oauth/login-dance/authorize [apache.commons.httpclient.HttpMethodDirector] Unable to respond to any of these challenges: {oauth=OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", oauth_problem="consumer_key_unknown"} 2012-06-19 14:50:39,559 http-8443-30 ERROR alexandre.alquier@sultan.com 890x58179x1 pocngl 82.127.114.234,127.0.0.1 /plugins/servlet/applinks/oauth/login-dance/authorize [core.auth.oauth.OAuthApplinksServlet] An error occurred when performing the oauth 'dance' for application link 'sultan (d138ac5b-109f-389b-a6fd-ed6acf8b5a80) https://sultan.onconfluence.com com.atlassian.applinks.application.confluence.ConfluenceApplicationTypeImpl@7db75f15' com.atlassian.sal.api.net.ResponseException: Failed to get token from service provider, problem was: 'consumer_key_unknown', full details: OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", oauth_problem="consumer_key_unknown" at com.atlassian.applinks.core.auth.oauth.OAuthTokenRetriever$1.handle(OAuthTokenRetriever.java:118) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$1.handle(JerseyRequest.java:142) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$1.handle(JerseyRequest.java:139) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:163) at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:307) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:158) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.execute(JerseyRequest.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.module.ContextClassLoaderSwitchingProxy.invoke(ContextClassLoaderSwitchingProxy.java:27) at $Proxy1365.execute(Unknown Source) {noformat} Common features effected by this issue is gadget subscription between JIRA and the other application such as confluence. *Workaround* Modify the timezones to match as per our [Setting the timezone for the JAVA environment|https://confluence.atlassian.com/display/JIRAKB/Setting+the+timezone+for+the+JAVA+environment] KB.
    via by Sultan Maiyaki [Atlassian],
    • com.atlassian.sal.api.net.ResponseException: Failed to get token from service provider, problem was: 'consumer_key_unknown', full details: OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", OAuth realm="https%3A%2F%2Fsultan.onconfluence.com", oauth_problem="consumer_key_unknown" at com.atlassian.applinks.core.auth.oauth.OAuthTokenRetriever$1.handle(OAuthTokenRetriever.java:118) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$1.handle(JerseyRequest.java:142) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$1.handle(JerseyRequest.java:139) at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:163) at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:307) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:158) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.execute(JerseyRequest.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.atlassian.plugins.rest.module.ContextClassLoaderSwitchingProxy.invoke(ContextClassLoaderSwitchingProxy.java:27) at $Proxy1365.execute(Unknown Source)
    No Bugmate found.