java.lang.NullPointerException

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.

  • If you have JIRA and Stash both using Crowd and having an application link between JIRA and Stash. If Stash is using an alias, then JIRA won't be able to see that alias and hence the source and commit tabs in JIRA would not show information from Stash. *Steps to reproduce* : # Set up Stash with users managed in Crowd # Set up JIRA with users managed in Crowd # Set an alias in Crowd for Stash users only. # Set up application link between JIRA ad Stash # Notice that in Stash the user is recognised with its alias and not username. # Try to browse an issue's Commit and Source tab in JIRA # The information would not be shown as JIRA does not see the user alias in Crowd. You will see an error like this in the logs : {noformat} 2014-06-03 10:27:59,473 ERROR [http-bio-8443-exec-13] 627x10922x0 54.80.233.142 "GET /mvc/error500 HTTP/1.1" c.a.s.i.web.ErrorPageController There was an unhandled exception loading [/rest/jira-dev/latest/detail/repository] java.lang.NullPointerException: null at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate2LORequest(AuthenticatorImpl.java:314) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate(AuthenticatorImpl.java:106) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.mayProceed(OAuthFilter.java:109) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.doFilter(OAuthFilter.java:62) ~[na:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doBeforeBeforeLoginFilters(BeforeLoginPluginAuthenticationFilter.java:89) ~[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doFilter(BeforeLoginPluginAuthenticationFilter.java:75) ~[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.request.DefaultRequestManager.doAsRequest(DefaultRequestManager.java:70) ~[stash-service-impl-3.0.1.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_55] ... 60 frames trimmed {noformat} *Workaround* For now the only workaround is to use aliases for JIRA as well.
    via by Ruchi Tandon[Atlassian],
  • If you have JIRA and Stash both using Crowd and having an application link between JIRA and Stash. If Stash is using an alias, then JIRA won't be able to see that alias and hence the Development Status in JIRA would not show information from Stash. *Steps to reproduce* : # Set up Stash with users managed in Crowd # Set up JIRA with users managed in Crowd # Set an alias in Crowd for Stash users only. # Set up application link between JIRA ad Stash # Notice that in Stash the user is recognised with its alias and not username. # Try to browse an issue's Development Status in JIRA # The information would not be shown as JIRA does not see the user alias in Crowd. You will see an error like this in the logs : {noformat} 2014-06-03 10:27:59,473 ERROR [http-bio-8443-exec-13] 627x10922x0 54.80.233.142 "GET /mvc/error500 HTTP/1.1" c.a.s.i.web.ErrorPageController There was an unhandled exception loading [/rest/jira-dev/latest/detail/repository] java.lang.NullPointerException: null at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate2LORequest(AuthenticatorImpl.java:314) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate(AuthenticatorImpl.java:106) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.mayProceed(OAuthFilter.java:109) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.doFilter(OAuthFilter.java:62) ~[na:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doBeforeBeforeLoginFilters(BeforeLoginPluginAuthenticationFilter.java:89) ~[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doFilter(BeforeLoginPluginAuthenticationFilter.java:75) ~[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.request.DefaultRequestManager.doAsRequest(DefaultRequestManager.java:70) ~[stash-service-impl-3.0.1.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_55] ... 60 frames trimmed {noformat} *Workaround* For now the only workaround is to use aliases for JIRA as well.
    via by Ruchi Tandon[Atlassian],
  • If you have JIRA and Stash both using Crowd and having an application link between JIRA and Stash. If Stash is using an alias, then JIRA won't be able to see that alias and hence the source and commit tabs in JIRA would not show information from Stash. *Steps to reproduce* : # Set up Stash with users managed in Crowd # Set up JIRA with users managed in Crowd # Set an alias in Crowd for Stash users only. # Set up application link between JIRA ad Stash # Notice that in Stash the user is recognised with its alias and not username. # Try to browse an issue's Commit and Source tab in JIRA # The information would not be shown as JIRA does not see the user alias in Crowd. You will see an error like this in the logs : {noformat} 2014-06-03 10:27:59,473 ERROR [http-bio-8443-exec-13] 627x10922x0 54.80.233.142 "GET /mvc/error500 HTTP/1.1" c.a.s.i.web.ErrorPageController There was an unhandled exception loading [/rest/jira-dev/latest/detail/repository] java.lang.NullPointerException: null at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate2LORequest(AuthenticatorImpl.java:314) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate(AuthenticatorImpl.java:106) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.mayProceed(OAuthFilter.java:109) ~[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.doFilter(OAuthFilter.java:62) ~[na:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doBeforeBeforeLoginFilters(BeforeLoginPluginAuthenticationFilter.java:89) ~[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doFilter(BeforeLoginPluginAuthenticationFilter.java:75) ~[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.request.DefaultRequestManager.doAsRequest(DefaultRequestManager.java:70) ~[stash-service-impl-3.0.1.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_55] ... 60 frames trimmed {noformat} *Workaround* For now the only workaround is to use aliases for JIRA as well.
    via by Ruchi Tandon[Atlassian],
    • java.lang.NullPointerException: null at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate2LORequest(AuthenticatorImpl.java:314)[na:na] at com.atlassian.oauth.serviceprovider.internal.AuthenticatorImpl.authenticate(AuthenticatorImpl.java:106)[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.mayProceed(OAuthFilter.java:109)[na:na] at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter.doFilter(OAuthFilter.java:62)[na:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doBeforeBeforeLoginFilters(BeforeLoginPluginAuthenticationFilter.java:89)[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.web.auth.BeforeLoginPluginAuthenticationFilter.doFilter(BeforeLoginPluginAuthenticationFilter.java:75)[BeforeLoginPluginAuthenticationFilter.class:na] at com.atlassian.stash.internal.request.DefaultRequestManager.doAsRequest(DefaultRequestManager.java:70)[stash-service-impl-3.0.1.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[na:1.7.0_55] at java.lang.Thread.run(Thread.java:744)[na:1.7.0_55]
    No Bugmate found.