Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1567

Trusted Applications + Application Aliasing will not work in Crowd. We need trusted applications to be 'enhanced' so we can provide a configurable user provider.

XMLWordPrintable

      Currently we cannot expect a username string in JIRA "justin" to equal the username string "justin@atlassian.com" in Confluence.

      For trusted apps to work JIRA and Confluence need to have both users to have the same name.

      With Application aliasing in Crowd we have complicated matters some what in allowing "justin" in JIRA to equal "justin@atlassian.com" in Confluence. However if their is a trust relationship between both these applications the 'trust' will fail for this user.

      This requires work to make the UserResolver in trusted apps 'plugable/configurable' so Crowd can correctly translate one username to another username for these requests.

            [CWD-1567] Trusted Applications + Application Aliasing will not work in Crowd. We need trusted applications to be 'enhanced' so we can provide a configurable user provider.

            Caspar Krieger (Inactive) added a comment -

            Closing this as obsolete because we expect users in app-linked Confluence and JIRA instances to have the same username; they both support user rename now, so even legacy systems should be able to meet this requirement.

            Caspar Krieger (Inactive) added a comment - Closing this as obsolete because we expect users in app-linked Confluence and JIRA instances to have the same username; they both support user rename now, so even legacy systems should be able to meet this requirement.

            Ryan Maki added a comment -

            I assume that this is the cause of the following warning throughout my Jira application logs when an aliased Fisheye user is attempting to view an activity stream in FE...

            2010-11-08 17:26:06,203 http-8080-11 WARN anonymous 1046x52130x1 - 10.x.x.x,127.0.0.1 /plugins/servlet/streams/local [auth.trustedapps.filter.TrustedApplicationFilterAuthenticator] User 'rmaki' referenced by trusted application: '_____' is not found.

            I've disabled Trusted Authentication for now in favor of OAuth, but that also doesn't work because Fisheye can't tell that the activity in Jira is associated with a Crowd user, because rmaki != ryan.maki, so each user shows up in multiple entries in the Activity Stream. "Ryan Maki" updated change list, then "ryan.maki" closed Jira issue.

            Are there any better workarounds if we are making heavy use of aliases between Jira, Fisheye, and Confluence? Thanks.

            Ryan Maki added a comment - I assume that this is the cause of the following warning throughout my Jira application logs when an aliased Fisheye user is attempting to view an activity stream in FE... 2010-11-08 17:26:06,203 http-8080-11 WARN anonymous 1046x52130x1 - 10.x.x.x,127.0.0.1 /plugins/servlet/streams/local [auth.trustedapps.filter.TrustedApplicationFilterAuthenticator] User 'rmaki' referenced by trusted application: '_____' is not found. I've disabled Trusted Authentication for now in favor of OAuth, but that also doesn't work because Fisheye can't tell that the activity in Jira is associated with a Crowd user, because rmaki != ryan.maki, so each user shows up in multiple entries in the Activity Stream. "Ryan Maki" updated change list, then "ryan.maki" closed Jira issue. Are there any better workarounds if we are making heavy use of aliases between Jira, Fisheye, and Confluence? Thanks.

              Unassigned Unassigned
              justin@atlassian.com Justin Koke
              Affected customers:
              3 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: