• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.5.2
    • 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.

      User aliases need to be managable via a remote API.

      This remote API should, at a minimum, allow:

      1. Query for all aliases of a user.
      2. Find the user with a given alias for a specific application
      3. Turning a user in directoryA into an alias of a user in directoryB. This is to allow 'claiming' of accounts.

            [CWD-1469] Remote API for managing user aliasing

            joe added a comment -

            The API this adds is:

            Resource Verb Content-Type Description
            /rest/appmanagement/1/aliases/<application-id>/alias?user=<username> GET, PUT, DELETE text/plain A user's alias in an application
            /rest/appmanagement/1/aliases/<application-id>/username?alias=<alias-or-username> GET text/plain The real username that the (possible) alias refers to
            /rest/appmanagement/1/aliases/?user=<username> GET application/json A hash from application-id to alias for all defined aliases

            As this is part of the appmanagement plugin, authentication is as a user in the crowd-administrators group.

            joe added a comment - The API this adds is: Resource Verb Content-Type Description /rest/appmanagement/1/aliases/<application-id>/alias?user=<username> GET, PUT, DELETE text/plain A user's alias in an application /rest/appmanagement/1/aliases/<application-id>/username?alias=<alias-or-username> GET text/plain The real username that the (possible) alias refers to /rest/appmanagement/1/aliases/?user=<username> GET application/json A hash from application-id to alias for all defined aliases As this is part of the appmanagement plugin, authentication is as a user in the crowd-administrators group.

            I cannot believe it's just not existing
            It was so logical for me that I started to write our migration process without checking that.
            No I see no other solution than manually editing aliases for my 160 users

            Arnaud Heritier added a comment - I cannot believe it's just not existing It was so logical for me that I started to write our migration process without checking that. No I see no other solution than manually editing aliases for my 160 users

              jwalton joe
              doflynn David O'Flynn [Atlassian]
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: