You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why is this needed? Since we must specify a specific cluster for the Kubernetes method and we cannot create a nested structure and add more than one cluster (more than one CA certificate, more than one JWT, and so on), we are forced to create a separate method for each cluster (for example, you don’t need to do this in the case of the AppRole method, when it is enough to create one single method of this type and add as many roles as you want). As a result, there can be a lot of methods in the UI, it would be more convenient to have a filter by method type.
The text was updated successfully, but these errors were encountered:
@Ais8Ooz8 thank you for the issue. We recently added filtering to the secret engine list view. I had a moment, so I snuck the same filtering (by name and type) into the auth method list view as well. This should be added in the 1.14 release. #20747
Why is this needed? Since we must specify a specific cluster for the Kubernetes method and we cannot create a nested structure and add more than one cluster (more than one CA certificate, more than one JWT, and so on), we are forced to create a separate method for each cluster (for example, you don’t need to do this in the case of the AppRole method, when it is enough to create one single method of this type and add as many roles as you want). As a result, there can be a lot of methods in the UI, it would be more convenient to have a filter by method type.
The text was updated successfully, but these errors were encountered: