IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 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;
          }
      

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 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;
                    }
                

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

                          Created:
                          Updated:
                          Resolved:

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

                              Created:
                              Updated:
                              Resolved: