# Management Console

T4K supports authentication via:

* [kubeconfig-authentication](https://docs.trilio.io/kubernetes/advanced-configuration/management-console/kubeconfig-authentication "mention")
* [oidc-ldap-and-openshift-authentication](https://docs.trilio.io/kubernetes/advanced-configuration/management-console/oidc-ldap-and-openshift-authentication "mention")
* [rbac](https://docs.trilio.io/kubernetes/advanced-configuration/management-console/rbac "mention")

If T4K has been installed at a **n**amespace level, then a minimum of *read access* over the namespace is required to access the management console.

Some Kubernetes clusters may contain cloud-specific `exec` action or use `auth-provider` configuration to fetch the authentication token within the kubeconfig file. Since the binaries for the specific cloud service may not be available on the setup where the user is providing the config file, T4K may not be able to fetch the token and populate it in the kubeconfig.

To support authentication for these cloud providers, perform the steps in the following sub-pages to create a kubeconfig file with a custom kubeconfig, consisting of a service account token and cluster data.