Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-3768

FishEye logs lots of ApplicationPermissionException when synchronising Crowd users that have no permission on FishEye / Crucible

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Fixed
    • 2.7.5
    • None
    • None
    • 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

      • no 'Groups to synchronise' have been configured and
      • FishEye is configured to periodically synchronise users from Crowd and
      • only limited groups have been granted access to FishEye in Crowd

      the following errors are logged when synchronising:

      2011-09-27 15:38:10,335 ERROR - Unexpected exception when retrieving token for user 'user.xyz'
      com.atlassian.crowd.exception.ApplicationPermissionException: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>APPLICATION_ACCESS_DENIED</reason><message>User does not have access to application &lt;FishEye&gt;</message></error>
      	at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.throwError(RestExecutor.java:414)
      	at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:300)
      	at com.atlassian.crowd.integration.rest.service.RestCrowdClient.authenticateSSOUserWithoutValidatingPassword(RestCrowdClient.java:819)
      	at com.cenqua.fisheye.user.crowd.CrowdAuth.canAuthenticate(CrowdAuth.java:278)
      	at com.cenqua.fisheye.user.crowd.CrowdAuth.access$500(CrowdAuth.java:54)
      	at com.cenqua.fisheye.user.crowd.CrowdAuth$3.call(CrowdAuth.java:241)
      	at com.cenqua.fisheye.user.crowd.CrowdAuth$3.call(CrowdAuth.java:235)
      	at com.cenqua.fisheye.user.crowd.CrowdAuth.withTimer(CrowdAuth.java:92)
      	at com.cenqua.fisheye.user.crowd.CrowdAuth.recreateAuth(CrowdAuth.java:235)
      	at com.cenqua.fisheye.user.DefaultUserManager.synchroniseUsers(DefaultUserManager.java:631)
      	at sun.reflect.GeneratedMethodAccessor165.invoke(Unknown Source)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
      	at com.googlecode.ehcache.annotations.interceptor.EhCacheInterceptor.invokeTriggersRemove(EhCacheInterceptor.java:191)
      	at com.googlecode.ehcache.annotations.interceptor.EhCacheInterceptor.invoke(EhCacheInterceptor.java:90)
      	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
      	at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
      

      The workaround is to configure the 'groups to synchronize' under Administration > Security Settings > Authentication > Jira or Crowd Authentication > Edit > Groups to synchronise

      Attachments

        Activity

          People

            mheemskerk Michael Heemskerk (Inactive)
            mheemskerk Michael Heemskerk (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: