User Story: Removing a Cluster from the Config (Version 2)

[Bhoomiz01]

Title:

As a user, I want the unified config file to exclude clusters I no longer have access to so that I only see authorized clusters.

---

Description:

When a user's access to a cluster is revoked, the unified configuration file is updated to exclude the removed cluster.

---

Acceptance Criteria:

1. Config Update:

   • When cluster access is revoked, the unified config file reflects the updated list, excluding the removed cluster.

2. Gangway Integration:

   • The "Download Config" button provides the updated file after cluster access is revoked.

3. Validation:

   • Users can download the updated config file and confirm the removed cluster is no longer accessible.

---

Steps for Validation:

1. Revoke the user’s access to an existing cluster.
2. Download the updated config from Gangway interface.
3. Ensure the updated config file excludes the removed cluster.
4. Verify that the user cannot access the removed cluster using the updated config.

[Bhoomiz01]

Note - When the admin revokes access to a cluster from the user and the user still uses the old config with that cluster, the user will not be able to access the cluster because the proxy will block any unauthorized request of the user.

[chintansakhiya]

@Bhoomiz01 @munir131 When a user downloads the configuration from the ops-dashboard, it includes the list of all clusters. However, the user can only access the clusters they have permission to access.