Description

When viewing the htpasswrd on the IDP page, at the bottom of the list of users, there will be a link to "View all users ( x )" where "x" is the total number of users if the user is an admin and has the feature gate enabled. This link will go to a htpasswrd IDP details page. In addition, there will be an option to "Edit users" in the action row of each htpasswrd IDP if the user is an admin user and has the feature gate enabled.

If the user is not an admin user or does not have the feature gate, the "edit users" option will not be available in the action menu.  In addition, if the user is not an admin or have the feature gate enabled then "( x more )" text will be at the bottom of the user list where "x" is the number of users beyond the 5 shown.

When a user activates either the link or the action, the user is taken to a htpasswrd IDP details page.  This page consists of a list of users for the chosen IDP page. The user list is paginated and can be sorted and filtered by name.  If there are no results (either because the htpasswrd does not have users or by filtering), then the PatternFly's empty state will be shown (see https://v5-archive.patternfly.org/components/empty-state#no-match-found).

This detail page will have a unique URL that can be bookmarked.  If a user goes to this direct or without the feature gate or is not an admin for the corresponding cluster, then the user will be navigated back to the IDP list on the cluster details page.  

Screenshots

NOTE: delete is not part of this story. While "edit" isn't technically correct yet - it will be used as the action text)

NOTE:  The name of the page title and the breadcrumbs is incorrect in the mock up.  They should be "View identity provider: htpasswrd".

------------------------------------

Technical details

To get the actual users for a given htpasswrd IDP, a secondary API call is needed to:

GET /api/clusters_mgmt/v1/clusters/{cluster_id}/identity_providers/{identity_provider_id}/htpasswd_users

It is unknown if this endpoint supports pagination, sorting, and/or filtering. If not, the UI will need to download all users for a given htpasswrd IDP and do the pagination, sorting, and filtering on the client.