...
- This is used for atlassian to know the complete list of groups. The implementation of the connector knows that something is an atlassian group since it is in the atlassian folder (configured somewhere in the folder structure). This could also be implemented with group "types" or labels on the group...
- Input takes a folder, in grouper's case also pass in if you want groups immediately in the folder, or if it can also be in any subfolder, in this case we need folder or subfolder
- The interface needs the group name returned, though grouper returns the group details (name, description, etc)
- Note, this is the same web service operation as "Find group by name"
Update group
- There is a "store" method in the interface for groups, which I would assume would edit the attributes, though the only attribute Atlassian uses is group name, and there is no way to edit that, so in this case I think the operation is a no-op, and only in the UserProvider interface for other reasons than for groups...