Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-8970

Consider adding a SOAP service to get all users

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently there is no (easy) way for a remote client to discover a list of all user in a Jira installation. The best that you can do (if you are an admin user) is call getUsers(Group) where group is the jira-users group. It would be really handy if there were a service to get a list of all users in the system. With this information it would be possible for remote clients to provide user lookup facilities and mappings between user id's and real names.

      However, I do understand that adding such a service opens the system up to abuse. It would be trivial to write a client that could harvest a list of valid email addresses from the system. Requiring the user to login before calling the service may help this a bit.

      Here is the RPC service code:

      UserServiceImpl.java
          public RemoteUser[] getAllUsers()
    {
    	Collection usersCollection = UserUtils.getAllUsers();
    	RemoteUser[] users = new RemoteUser[usersCollection.size()];
    	
    	int i = 0;
    	for (Iterator iUsers = usersCollection.iterator(); iUsers.hasNext(); i++) {
    		users[i] = new RemoteUser((User) iUsers.next());
    	}
        return users;
    }

            [JRASERVER-8970] Consider adding a SOAP service to get all users

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3046786 ] New: JAC Suggestion Workflow 3 [ 3691306 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Component/s Original: Ecosystem - SOAP & XML-RPC API [Obsolete] [ 10480 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2605958 ] New: JAC Suggestion Workflow [ 3046786 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2557302 ] New: Confluence Workflow - Public Facing v4 [ 2605958 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347255 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2557302 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2113875 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347255 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091841 ] New: JIRA Bug Workflow w Kanban v6 [ 2113875 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 880064 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091841 ]
            jonah (Inactive) made changes -
            Description Original: Currently there is no (easy) way for a remote client to discover a list of all user in a Jira installation. The best that you can do (if you are an admin user) is call getUsers(Group) where group is the jira-users group. It would be really handy if there were a service to get a list of all users in the system. With this information it would be possible for remote clients to provide user lookup facilities and mappings between user id's and real names.

            However, I do understand that adding such a service opens the system up to abuse. It would be trivial to write a client that could harvest a list of valid email addresses from the system. Requiring the user to login before calling the service may help this a bit.

            Here is the RPC service code:

            {code:title=UserServiceImpl.java}
                public RemoteUser[] getAllUsers()
                {
                 Collection usersCollection = UserUtils.getAllUsers();
                 RemoteUser[] users = new RemoteUser[usersCollection.size()];
                
                 int i = 0;
                 for (Iterator iUsers = usersCollection.iterator(); iUsers.hasNext(); i++) {
                 users[i] = new RemoteUser((User) iUsers.next());
                 }
                    return users;
                }
            {code}             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-8970].
              {panel}

            Currently there is no (easy) way for a remote client to discover a list of all user in a Jira installation. The best that you can do (if you are an admin user) is call getUsers(Group) where group is the jira-users group. It would be really handy if there were a service to get a list of all users in the system. With this information it would be possible for remote clients to provide user lookup facilities and mappings between user id's and real names.

            However, I do understand that adding such a service opens the system up to abuse. It would be trivial to write a client that could harvest a list of valid email addresses from the system. Requiring the user to login before calling the service may help this a bit.

            Here is the RPC service code:

            {code:title=UserServiceImpl.java}
                public RemoteUser[] getAllUsers()
                {
                 Collection usersCollection = UserUtils.getAllUsers();
                 RemoteUser[] users = new RemoteUser[usersCollection.size()];
                
                 int i = 0;
                 for (Iterator iUsers = usersCollection.iterator(); iUsers.hasNext(); i++) {
                 users[i] = new RemoteUser((User) iUsers.next());
                 }
                    return users;
                }
            {code}
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-8970 [ JRACLOUD-8970 ]

              Unassigned Unassigned
              13b349c87b4b Brock Janiczak
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: