With an external user directory(ies), the “rest/api/2/group/member” endpoint is extremely slow to respond (~2.5+ minutes), even when limiting the response size to the first 50 users.

If the current approach can’t be sped up, as an admin, I’d like the ability to check group membership against cached/potentially stale results (with an extra query param flag or something similar).

The current behavior goes directly to the database and examines the contents of all user directories, with a lot of churn to handle duplicate user names across directories.

• Environment:- Jira + Embedded crowd

 h5. Replication:

• Have more than 1000 users in External directory (ies)
• Call both the API's (as the error observed in both the API's are same)

 https://base-url/rest/api/2/group/member?groupname=jira-users&startAt=0&maxResults=49 

https://base-url/rest/api/2/group?groupname=jira-users&expand=users&startAt=0&maxresult=49