Bar Chart Plugin isn't working

[Ken Mihara]

I just installed the Jira Bar Chart Plugin today, and created a gadget on the dashboard that was working just fine. Then I went to try and reconfigure the refresh interval, and now I am getting the following error message: "status-code", 401, "message";"Client must be authenticated to access this resource." I have tried to uninstall and reinstall the bar chart plugin, and still am getting the same error. Please Help!

Thank you.

[William Gunkel]

I am on JIRA 6.3.100 with Bar Chart 2.6 and having the same issue

[Greg Hoggarth]

I am on 6.2 and am having this problem.

[Chris Lieb]

Ditto and using latest version of the plugin. Same old non-sensical 401 error.

[Jan Osmers]

At the moment we are working with Jira 6.0.5 and plugin version 2.4. With those versions we never experienced this authentication issue any more.

The problem may be an invalid cookie or browser cache. Try another browser if possible from another machine.

HTH

[Ruben Straube]

Please try the new plugin version 2.6, as we made some changes to avoid REST collisions with other plugins. If the problem still occurs, please tell us!

[Papa]

The problem still occurs with version 2.6...

[Sabina H_]

We're having issues as well after the upgrade to the latest version of the gadget. Here's what our logs say: 2014-09-24 23:07:29,411 http-bio-8080-exec-17 ERROR ((USERNAME_DELETED_FOR_THIS_POST)) 967x7119x2 1a3khkp 198.74.40.20,10.130.3.102 /plugins/servlet/gadgets/makeRequest [renderer.internal.http.HttpClientFetcher] Unable to retrieve response javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated at sun.security.ssl.SSLSessionImpl.getPeerCertificates(Unknown Source) at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:126) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:437) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557) at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher$CustomSSLSocketFactory.connectSocket(HttpClientFetcher.java:193) at org.apache.http.conn.scheme.SchemeSocketFactoryAdaptor.connectSocket(SchemeSocketFactoryAdaptor.java:65) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180) at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:294) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:643) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784) at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.fetch(HttpClientFetcher.java:111) at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchFromServer(OAuthFetcher.java:802) at org.apache.shindig.gadgets.oauth.OAuthFetcher.sendOAuthMessage(OAuthFetcher.java:581) at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchRequestToken(OAuthFetcher.java:334) at org.apache.shindig.gadgets.oauth.OAuthFetcher.attemptFetch(OAuthFetcher.java:274) at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchWithRetry(OAuthFetcher.java:230) at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchNoThrow(OAuthFetcher.java:188) at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetch(OAuthFetcher.java:169) at org.apache.shindig.gadgets.http.ContentFetcherFactory.fetch(ContentFetcherFactory.java:54) at com.atlassian.gadgets.renderer.internal.http.TrustedAppContentFetcherFactory.fetch(TrustedAppContentFetcherFactory.java:47) at org.apache.shindig.gadgets.servlet.MakeRequestHandler.fetch(MakeRequestHandler.java:84) at org.apache.shindig.gadgets.servlet.MakeRequestServlet.doGet(MakeRequestServlet.java:55) at com.atlassian.gadgets.shindig.servlet.XsrfMakeRequestServlet.doGet(XsrfMakeRequestServlet.java:32) at org.apache.shindig.gadgets.servlet.MakeRequestServlet.doPost(MakeRequestServlet.java:65) at com.atlassian.gadgets.shindig.servlet.XsrfMakeRequestServlet.doPost(XsrfMakeRequestServlet.java:47) at javax.servlet.http.HttpServlet.service(HttpServlet.java:647) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:42) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at com.atlassian.plugin.servlet.ServletModuleContainerServlet.service(ServletModuleContainerServlet.java:52) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) <+2> (ApplicationFilterChain.java:305) (ApplicationFilterChain.java:210) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) <+14> (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210) (ChainedFilterStepRunner.java:87) (ApplicationFilterChain.java:243) (ApplicationFilterChain.java:210)

[Ruben Straube]

Hey everyone having issues with the Barcharts plugin and JIRA 6.1.x,

we ran into compatibility problems from 6.1.4 onwards. This was due to some internal changes, which is why you see the error messages coming from TrustedApps, that the user was unauthorized.

Before we had the time to look into and fix that problem, we found that it works fine with JIRA 6.2. So unfortunately, it looks like there will be a 'support gap' between 6.1.4 and 6.1.7, since it currently does not look like as if we have time to see what had caused that problem.

If you want to, you are welcome to look at the source code at https://bitbucket.org/tngtech/barcharts-for-jiraas the plugin is open source.

Kind regards,

Ruben

[Subhendu Chattopadhyay]

I am on 6.2.6 and having same problem :(

[anusha ch]

I am using 2.5.2 version of bar chart plugin in Jira 6.2.5 and having same issue :(

[Ruben Straube]

Please try the new version 2.6, as we made some changes to avoid REST collisions with other plugins. If the problem still occurs, please tell us!

[Papa]

I had the same issue with Barchart 2.5.1 and Jira 6.1.7.

After uninstalling the plugin and installing Barchart 2.5 it started to work.
Then uninstalling 2.5 and installing 2.5.1 and it continued to work.

So I don't know If uninstalling and reinstalling or going one version back did the trick.

HTH

[AndreasS]

Can anybody reprocue this or just have the problem even after re-installing the plugin?

[Chris Kent]

We have just run into this, I cleared my cache and cookies and noticed this error???

We have JIRA 6.1.1 and the latest Barchart 2.5.1 plugin at this time.

Actually does this on IE and Chrome, so likely nothing to do with cookies/cache as I don't normally use IE.

I just tried to uninstall 2.5.1 and try 2.5 - no luck, stilll has client authentication error.

The exaclt error I get is: {"message":"Client must be authenticated to access this resource.","status-code":401}

[Jan Osmers]

Hi Rick,

we have had this problem as well on our site. Please consider to Update to Jira 5.1.8 at least and plugin version 2.4.

Regards,

Jan

[AndreasS]

Has that helped for anyone?

[Rick Carini]

Hi! Did anyone ever get this fixed? I loaded this plugin last week for the first time and a few days later received both the error listed above as well as the errors seen in the log file above. I have a fairly old version of JIRA at v5.0.3 with plugin version of 2.3.1 since this is listed as the version supporting jira 5.0.3.

Thanks!

Rick

[Rick Carini]

Hi! Did anyone ever get this fixed? I loaded this plugin last week for the first time and a few days later received both the error listed above as well as the errors seen in the log file above. I have a fairly old version of JIRA at v5.0.3 with plugin version of 2.3.1 since this is listed as the version supporting jira 5.0.3.

Thanks!

Rick

[Michael Bernard]

Hi, I have the same behavior.

The error occurs without any configuration. When I add the plugin to the dashboard, it produces that error.Please note that: I changed the IP and the user.

Here is the trace from the log:

2012-08-01 09:16:51,835 StreamsCompletionService::thread-20768 WARN USER 556x408945x1 1iti42j 0.0.0.0 /rest/activity-stream/1.0/config [atlassian.streams.internal.AppLinksActivityProvider] Unable to retrieve filter options from /rest/activity-stream/1.0/config?local=true

2012-08-01 09:16:51,913 http-80-15 WARN USER 556x408952x6 1iti42j 0.0.0.0 /plugins/servlet/gadgets/makeRequest [http.impl.client.DefaultRequestDirector] Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2Fca-rd-jira", oauth_problem="consumer_key_unknown"}

2012-08-01 09:16:51,928 http-80-37 WARN USER 556x408951x5 1iti42j 0.0.0.0 /plugins/servlet/gadgets/makeRequest [http.impl.client.DefaultRequestDirector] Authentication error: Unable to respond to any of these challenges: {oauth=WWW-Authenticate: OAuth realm="http%3A%2F%2Fca-rd-jira", oauth_problem="consumer_key_unknown"}

2012-08-01 09:16:53,444 http-80-15 ERROR USER 556x408959x5 - 0.0.0.0 /rest/jira-rest/1.0/BarChart/GenerateChart [plugins.utils.fields.CustomFieldWrapper] Could not retrieve name from non existant custom field!

2012-08-01 09:16:53,444 http-80-15 ERROR USER 556x408959x5 - 0.0.0.0 /rest/jira-rest/1.0/BarChart/GenerateChart [plugins.utils.fields.CustomFieldWrapper] Could not retrieve name from non existant custom field!

2012-08-01 09:16:53,444 http-80-15 ERROR USER 556x408959x5 - 0.0.0.0 /rest/jira-rest/1.0/BarChart/GenerateChart [plugins.utils.fields.CustomFieldWrapper] Could not retrieve name from non existant custom field!

2012-08-01 09:16:53,444 http-80-15 ERROR USER 556x408959x5 - 0.0.0.0 /rest/jira-rest/1.0/BarChart/GenerateChart [plugins.utils.fields.CustomFieldWrapper] Could not retrieve name from non existant custom field!

Thanks,Michael

[Ed Costello]

Getting the same error suddenly today. Try to edit the gadget and see the Filter field is blank. Added the filter, apply the change and the error occurs. Back to edit mode and the Filter field is blank. All other gadget configuration fields are unchanged.