Listing Members with Access to Images and Helm Charts

When FlexNet Operations creates a project in the registry, information about producer users and entitled end-users that are associated with the download package in FlexNet Operations is automatically propagated to the registry. This includes:

•

All producer users from the producer account and its sub-accounts who have the "View and Manage Download Packages" permission. In the registry, these producer users are added as “members” to the project.

•

All end-users who are entitled to the download package and have the "Get Downloads" permission.

The /projects/{project_name}/members endpoint returns a list of the members who have access to a particular project. The name of the project must be passed in the {project_name} parameter.

To retrieve information about a particular member, specify their user name using the query parameter user_id (the user_id is identical with the entityName field in the response).

Important: If you are using a shared registry, the project names are automatically prefixed with your 4-character tenant ID. Omit this tenant ID when you specify the project name. For example, if your project name is 1234-1000-project1-April2020 (where 1234 is your tenant ID), use the URI /registry/api/v1/projects/1000-project1-April2020.

Item	Description
URI	/registry/api/v1/projects/{project_name}/members
Method	GET
Query parameters	• page: Retrieves a specific page. Must be a number. Default: 1. • page_size: Specifies how many records per page should be returned. Must be a number. Default: 10. • project_name: The name of the project for which information is requested. Required path parameter. • user_id: Retrieves information about a particular member.
Request body	N/A
Response codes	200: Success 400: Bad request 401: Unauthorized 404: Project not found 500: Internal server error

Sample Response

The following shows a sample response for a successful GET call, where no particular member was specified (therefore, all members with access to the project are returned):

[

{

"roleName": "projectAdmin",

"entityName": "AdminRegistryUser",

"projectId": 1234

},

{

"roleName": "developer",

"entityName": "user1@mycompany.com",

"projectId": 1234

},

{

"roleName": "developer",

"entityName": "user2@mycompany.com",

"projectId": 1234

},

{

"roleName": "developer",

"entityName": "user3@mycompany.com",

"projectId": 1234

},

]

Note: In the output, the entityName field is equivalent to a member’s user_id.