Uploaded image for project: 'Crowd'
  1. Crowd
  2. CWD-3960

Applications connected using application link not able to see the Crowd aliases of other application

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Applications
    • Labels:
      None
    • UIS:
      1
    • Support reference count:
      1
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      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 :

      1. Set up Stash with users managed in Crowd
      2. Set up JIRA with users managed in Crowd
      3. Set an alias in Crowd for Stash users only.
      4. Set up application link between JIRA ad Stash
      5. Notice that in Stash the user is recognised with its alias and not username.
      6. Try to browse an issue's Commit and Source tab in JIRA
      7. 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 :

      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
      

      Workaround
      For now the only workaround is to use aliases for JIRA as well.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              rtandon@atlassian.com Ruchi Tandon
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: