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

Allow searching for user by key from admin interface

    • Icon: Suggestion Suggestion
    • Resolution: Invalid
    • None
    • Core features
    • 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.

      This would allow us to find which user corresponds to a particular key in environments with restricted access to the REST API/database.

            [CWD-4234] Allow searching for user by key from admin interface

            If you have a particular key and want to find the matching user, you can use something like: curl http://localhost:8095/crowd/rest/usermanagement/1/user?key=theopaquekeyoftheuser

            Is that enough for you hgiddens? While the Crowd UI would clearly be more convenient, you can always use the admin UI to give yourself access to the REST API.

            Since the key was introduced (afaik) just to support user renames in connected apps as an opaque value and we haven't even documented it (CWD-4069), I don't think it makes sense to expose it as a first class concept in the Admin UI.

            Caspar Krieger (Inactive) added a comment - If you have a particular key and want to find the matching user, you can use something like: curl http://localhost:8095/crowd/rest/usermanagement/1/user?key=theopaquekeyoftheuser Is that enough for you hgiddens ? While the Crowd UI would clearly be more convenient, you can always use the admin UI to give yourself access to the REST API. Since the key was introduced (afaik) just to support user renames in connected apps as an opaque value and we haven't even documented it ( CWD-4069 ), I don't think it makes sense to expose it as a first class concept in the Admin UI.

              Unassigned Unassigned
              hgiddens Hugh Giddens (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: