https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/Recent content in Connect an external service onHugo -- gohugo.ioTue, 06 Oct 2020 08:48:23 +0000https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/authentication/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/authentication/The Shturval platform is compatible with external authentication services using the OIDC OAuth 2.0 protocol. To connect an external authentication service, follow the steps for preparing to configure the connection of an external service in the platform. You can connect external authentication services: Keycloak; Blitz. When services such as ArgoCD, Grafana are running in the management cluster, then when changing the authentication service, changes in ssc will not be required.https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/keycloak/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/keycloak/Once you have completed the steps to prepare for setting up a connection in the platform (the configuration of the external authentication service has been received), you can make changes to the ssc of the Authentication Management Module (shturval-auth) from the command line interface or from the GUI. It is recommended to connect external authentication services from the command line interface (console). Connect from the command line interface # Log in to the “Shturval” platform using the kubeconfig received during platform installation, or you can take it from the Control Plane of the /etc/kubernetes/admin.https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/blitz/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/blitz/When the steps to prepare for setting up a connection in the platform have been completed (the configuration of the external authentication service has been received): Log in to the “Shturval” platform using the kubeconfig received during platform installation, or you can take it from the Control Plane of the /etc/kubernetes/admin.conf platform node. Get ssc shturval-auth and save the original ssc so you can quickly roll back changes in case of an error:https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/troubleshooting/Mon, 16 Nov 2020 13:59:39 +0100https://docs.shturval.tech/2.13/en/cluster-admin/howto/auth/externalprovider/troubleshooting/Let’s say that in the “Shturval” platform you have connected an external service for authentication, for example, Keycloak or Blitz. There are situations when a failure may occur on the side of the external authentication service. In this case, it is possible to disable the external authentication service and restore access to the platform for all users. To ensure that work in the platform is not interrupted if an external service fails, do the following: