Skip to content

get_all_organization_members should support fields #534

Closed

Description

@freyamade

Checklist

  • I have looked into the Readme and Examples, and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

The endpoint for fetching all Organization members allows us to pass a fields parameter, specifically to include all member's roles in the response. The python library hides this option, and it would be much more performant to allow us to get all roles attached in one request instead of n^2 requests to fetch all users and then each user's roles in a separate request for each.

Describe the ideal solution

There are two ways it could play out, either by adding a include_roles flag, or by providing access to add more paramters via ** args to this and other functions.

Alternatives and current workarounds

The current way we have to do this is to do the following;

  1. Fetch all users in an organization
  2. Iterate over each user, sending a new request to fetch that user's roles specifically

Alternatively, we have been accessing variables and functions we shouldn't be, running something like;

auth0.organizations.client.get(auth0.organizations._url('<org_id>', "members"), params=dict(fields='user_id,name,email,roles'))

Additional context

No response

Activity

  1. added
    feature requestA feature has been asked for or suggested by the community
    on Oct 11, 2023
  2. adamjmcgrath commented on Oct 12, 2023

    @adamjmcgrath
    Contributor

    Thanks for raising this @freyamade - We have some work planned to update the SDKs with this new parameter, should happen in the next couple of weeks

  3. freyamade commented on Oct 13, 2023

    @freyamade
    Author

    Thank you so much 🙏

  4. added a commit that references this issue on Oct 19, 2023
    823e58f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestA feature has been asked for or suggested by the community

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions