docs: Revamp SSO Login Services Page

docs/user-guide/global-configurations/sso-login.md

@@ -1,67 +1,49 @@
 # SSO Login Services
 
-Once Devtron is installed, it has a built-in `admin` user with super admin privileges with unrestricted access to all Devtron resources. We recommended to use a user with super admin privileges for initial and global configurations only and then switch to local users or configure SSO integration.
+## Introduction
 
-Only users with [super-admin](../global-configurations/authorization/user-access.md#grant-super-admin-permission) privileges can create SSO configuration. Devtron uses [Dex](https://dexidp.io/docs/connectors/google/) for authenticating a user against the identity provider.
+After successful installation of Devtron, when you login for the first time with the [Admin Credentials](../../setup/install/install-devtron-with-cicd.md) provided during the initial setup, you will have [Super-Admin](user-access.md) privileges with unrestricted access to all Devtron resources including configuring SSO and creating new user permissions.
 
+Therefore, we highly recommend that you also create and manage necessary [User Permissions](user-access.md) for other users immediately after configuring the SSO, to ensure secure and streamlined access to Devtron. 
 
-To add/edit SSO configuration, go to the `SSO Login Services` section of `Global Configurations`. 
+Devtron uses Dex to authenticate you against the identity providers such as GitHub, GitLab, Google, Microsoft, LDAP, OIDC, and OpenShift.
 
-## Supported SSO Providers
-
-Below are the SSO providers which are available in Devtron. Select one of the SSO providers (e.g., GitHub) to configure SSO:
+---
 
-[Google](./authorization/sso/google.md)
-[GitHub](./authorization/sso/github.md)
-[GitLab](./authorization/sso/gitlab.md)
-[Microsoft](./authorization/sso/microsoft.md)
-[LDAP](./authorization/sso/ldap.md)
-[OpenID Connect](./authorization/sso/oidc.md)
-[OpenShift](./authorization/sso/openshift.md)
+## Supported SSO Providers
 
-Dex implements connectors that target specific `identity providers` for each connector configuration. You must have a created account for the corresponding identity provider and registered an app for client key and secret.
+To configure SSO in Devtron, navigate to **Global Configurations** → **Authorizations** → **SSO Login Services**. The SSO Login Services page is displayed.
 
-Refer the following documents for more detail.
-* https://dexidp.io/docs/connectors/
-* https://dexidp.io/docs/connectors/google/
+![Figure 1: Supported SSO Providers](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/global-configurations/sso-login-service/sso-login-home.jpg)
 
+Devtron supports the following SSO providers:
 
-### 1. Create new SSO Configuration
+* [Google](./authorization/sso/google.md)
 
-Make sure that you have a [super admin access](../global-configurations/authorization/user-access.md#grant-super-admin-permission).
+* [GitHub](./authorization/sso/github.md)
 
-* Go to the `Global Configurations` → `SSO Login Services` and click any `SSO Provider` of your choice.
-* In the `URL` field, enter the valid Devtron application `URL` where it is hosted.
-* For providing `redirectURI` or `callbackURI` registered with the SSO provider, you can either select `Configuration` or `Sample Script`.
-* Provide the `client ID` and `client Secret` of your SSO provider (e.g. If you select `Google` as SSO provider, then you must enter `$GOOGLE_CLIENT_ID` and `$GOOGLE_CLIENT_SECRET` in the `client ID` and `client Secret` respectively.)
-* Select `Save` to create and activate SSO Login Service.
+* [GitLab](./authorization/sso/gitlab.md)
 
+* [Microsoft](./authorization/sso/microsoft.md)
 
-**Note**: 
-* Only single SSO login configuration can be active at one time. Whenever you create or update any SSO configuration, it will be activated and used by Devtron and previous configurations will be deleted.
-* Except for the domain substring, URL and redirectURI remains same.
+* [LDAP](./authorization/sso/ldap.md)
 
-![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/global-configurations/sso-login-service/sso-login-services.jpg)
+* [OpenID Connect](./authorization/sso/oidc.md)
 
+* [OpenShift](./authorization/sso/openshift.md)
 
-### 2. Update SSO Configuration
+Only one SSO configuration can be active at a time. Display of multiple SSO configurations is currently not supported on Devtron's login page. When you create a SSO configuration, for e.g., Google, the Google SSO configuration is made active and will be used by Devtron for authentication.  
 
-You can change SSO configuration anytime by updating the configuration and click `Update`.
-**Note**: In case of configuration change, all users will be logged out of Devtron and will have to login again.
+{% hint style="warning" %}
 
+### Note
 
-### 3. Configuration Payload
+If Google SSO is configured in Devtron, for example, and multiple users have logged in using it, changing the SSO configuration from Google to GitHub or any other providers will forcibly sign out all users who were logged in with Google SSO.
 
-* `type` : Any platform name such as (Google, GitLab, GitHub etc.) 
-* `name` : Identity provider platform name 
-* `id` : Identity provider platform which is a unique ID in string. (Refer to [dexidp.io](https://dexidp.io/)
-* `config` : User can put connector details for this key. Platforms may not have same structure but common configurations are `clientID`, `clientSecret`, `redirectURI`.
-* `hostedDomains` : Domains authorized for SSO login.
+{% endhint %}
 
 ---
 
 ## Next Steps
 
-After configuring an SSO for authentication, you need to [add users](./authorization/user-access.md#add-users) in Devtron, else your users won't be able to log in via SSO. 
-
-In case you have enabled auto-assign permissions in [Microsoft](./authorization/sso/microsoft.md) or [LDAP](./authorization/sso/ldap.md), relevant [permission groups](./authorization/permission-groups.md#add-group) must also exist in Devtron for a successful login.
+The next step is to select your preferred SSO login service from the available list of providers and set up the SSO configuration.