XMLRPC plugin needs an interface to get identifiable user information user.info()

This could be added to AccountManagerPlugin or perhaps user session introspection could be added to XmlRpcPlugin.

I have made a version that returns the env.get_known_users() call - customised for our particular setup in several ways, but very easy to implement in a straight forward fashion (untested example implementation):

def getKnownUsers(self, req):
    """ Docs :-) """
    return self.env.get_known_users()

It allows us implement 'assign-to' as a drop-down in a custom ticket form, for instance.

The implementation is very easy - the difficult part with this is actually determining permissions - what permission should be required to fetch this list? It has many possible uses, not just tickets. However, it is easy to see that data can very easily be abused with relaxed permissions in public projects.

This calls for some precautions, and my feeling is that user-related features need to be spread out across various modules, and highly tuned to specific tasks and permissions.

• An implementation for ticket.getKnownUsers() should perhaps just return the username for populating drop-downs (to assign), and perhaps only return data if the restrict config setting is enabled - and using corresponding ticket permissions.
• The full-list example above could perhaps require TRAC_ADMIN?
• An implementation for the AccountManagerPlugin to view and modify data belong in that plugin, and tuned to the needs and permissions of corresponding methods there (likely all TRAC_ADMIN).

Ah, just noticed #1010 that explicitly request the ticket.getKnownUsers()-like aspect of this.

As this ticket is somewhat ambiguous (potentially covering several plugins), I suggest:

• This ticket is moved to AccountManagerPlugin as a request for xmlrpc features added to that plugin.
• And, the ticket-drop-down-related part is continued in #1010 as a possible extension to standard XmlRpcPlugin.