# Social Logins -------------------------------------------------------------------------------- title: "Introduction" description: "Catalyst Authentication enables you to provide secure authentication and sign-ins for your app users, and manage their user accounts." last_updated: "2026-03-18T07:41:08.533Z" source: "https://docs.catalyst.zoho.com/en/cloud-scale/help/authentication/social-logins/introduction/" service: "Cloud Scale" -------------------------------------------------------------------------------- # Social Logins Catalyst enables you to allow your end users to log on to your application using popular Identity Providers (IdP) or *Social Logins*. You can configure and add social logins to your login element directly from the console. {{%note%}}{{%bold%}}Note:{{%/bold%}} To enable Social Logins, you must first enable {{%link href="/en/cloud-scale/help/authentication/public-signup" %}}Public Signup{{%/link%}}{{%/note%}} Catalyst offers support for you to implement the following social logins: * {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-zoho-social-login" %}}Zoho{{%/link%}} * {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-google-social-login" %}}Google{{%/link%}} * {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-facebook-social-login" %}}Facebook{{%/link%}} * {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-linkedin-social-login" %}}LinkedIn{{%/link%}} * {{%link href="/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/#enable-microsoft-365-social-login" %}}Microsoft 365{{%/link%}} These social logins can be configured with Catalyst by utilizing the industry standard OAuth protocol, i.e., by configuring the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} for your Catalyst application provided by the IdP service. {{%note%}}{{%bold%}}Note:{{%/bold%}} Catalyst offers you support to implement these social logins directly from the console in both its {{%link href="/en/cloud-scale/help/authentication/native-catalyst-authentication/introduction/" %}} Native Catalyst Authentication types{{%/link%}}. However, should you wish to implement them while using {{%link href="/en/cloud-scale/help/authentication/third-party-authentication/introduction/" %}}Third Party Authentication{{%/link%}}, you will have to code the logic.{{%/note%}} ### Benefits * Enabling your end-users to log in to your application using Social Logins aids them in accessing your application easily and quickly without compromising security. It provides them with a more streamlined login experience by eliminating password fatigue and making it more mobile-friendly. * Catalyst provides support to manage the backend requirements of implementing social logins in your login element. You can easily enable them once you set up the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} from your preferred Identity Providers (IdP). * You can configure a login element with {{%link href="/en/cloud-scale/help/authentication/native-catalyst-authentication/embedded-authentication/introduction/" %}}Embedded Authentication{{%/link%}} that authenticates users using only Social Logins. This lets you authenticate users securely with minimal efforts. * You can enable and disable them per your preference directly from the console, with no additional coding. * By implementing Social Logins on your application you also reduce the chance for fake accounts. ### Configure Authorized URIs To enable Social Logins for your application, you require an authorized URI to generate the required client tokens. The steps to configure the Authorized URI is the same for all of the Social Logins, for the purposes of this help document, we are goin to illustrate the steps using the Google Social Login: 1. Click the required social login, from the console: <br /> 2. Copy the Authorized URI, and replace the placeholders as instructed in the console <br /> {{%note%}}{{%bold%}}Key Terminology{{%/bold%}} * {{%badge%}}{{%bold%}}appdomain{{%/bold%}}{{%/badge%}}: {{%badge%}}appdomain{{%/badge%}}is a placeholder in the Authorized URI generated by Catalyst. It is a place holder for the domain of your application. Your application's domain will be generated and listed in the {{%link href="/en/cloud-scale/help/web-client-hosting/introduction/" %}}Web Client Hosting{{%/link%}} component after you deploy your application to the console. You can also add a cusotm domain that tou have mapped to your application. * {{%badge%}}{{%bold%}}ZAID{{%/bold%}}{{%/badge%}}: {{%badge%}}ZAID{{%/badge%}} is a unique portal ID generated by Catalyst to map your project to the right environment.{{%/note%}} For example, The URI when its first copied, will be in the following format: **https://{{appdomain}}/accounts/pfs/{{dev or prod zaid}}/clientidpcallback** To make this a valid URI, copy your app domain and replace it with the **{{appdomain}}** placeholder and copy the development {{%badge%}}ZAID{{%/badge%}} value and replace it with the **{{dev or prod zaid}}** placeholder. Your completed URI will resemble the following URI: **https<span></span>://authorizationportal-779513891.development.catalystserverless.com/accounts/pfs/1011958529/clientidpcallback** {{%note%}}{{%bold%}}Note:{{%/bold%}} * While configuring the Authorized URI to a valid URI, you can also use a custom domain of your choice. * When you migrate your application to production, you need to reconfigure the social logins using the the production {{%badge%}}appdomain{{%/badge%}} and production {{%badge%}}ZAID{{%/badge%}}, for the social logins to function in the production environment.{{%/note%}} -------------------------------------------------------------------------------- title: "Configure Social Logins" description: "Catalyst Authentication enables you to provide secure authentication and sign-ins for your app users, and manage their user accounts." last_updated: "2026-03-18T07:41:08.534Z" source: "https://docs.catalyst.zoho.com/en/cloud-scale/help/authentication/social-logins/configuring-social-logins/" service: "Cloud Scale" -------------------------------------------------------------------------------- # Configure Social Logins Before you enable Social Logins while setting up an authentication method, you must complete certain steps to ensure you have the required {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} for each service that you require. This involves configuring an app in the respective social login's developer console, and fetching the OAuth credentials. You will also need to have your own account with each of the Social Login providers to access their developer consoles. {{%note%}}{{%bold%}}Note:{{%/bold%}} {{%link href="/en/cloud-scale/help/authentication/public-signup/" %}}Public Signup{{%/link%}} must be enabled to use Social Logins.{{%/note%}} ### Enable Zoho Social Login To enable Zoho sign in option in your application, you need to acquire the OAuth credentials for your application from the Zoho API Console in the following manner: 1. Navigate to the **Zoho API Console** from {{%link href="https://api-console.zoho.in/" %}}here{{%/link%}}, and click **ADD CLIENT**. <br /> 2. Select **Server-based Applications**, and click **CREATE NOW**. <br /> 3. Provide the name of your application as the client name. <br /> 4. Provide the **Homepage URL**, and the required **Authorized Redirect URIs**. * You can get the Authorized Redirect URIs, by following the steps detailed in this {{%link href="/en/cloud-scale/help/authentication/social-logins/introduction/#configure-authorized-uris" %}}help document{{%/link%}}. * Ensure you enter the redirect URIs of your application in the following format: - {{%bold%}}https<span>://accounts.zohoportal.com/accounts/extoauth/ZAID/clientcallback{{%/bold%}} - {{%bold%}}https<span>://{{appdomain}}/accounts/pfs/ZAID/clientidpcallback{{%/bold%}} <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} To ensure that the Social Logins are enabled when you migrate your app to production, you need to reconfigure them using the {{%badge%}}Production ZAID{{%/badge%}}, and the appropriate app domain.{{%/note%}} 5. Click **CREATE**. The required {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} values will be displayed. <br /> 6. You can copy the required {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} credentials from the API console and paste it in the respective fields in the Catalyst console, and click **Enable**. <br /> Your end users can now sign up to your application using their Zoho credentials. ### Enable Google Social Login To enable Google sign in option in your application, you must obtain the required OAuth credentials for your application from Google in the following manner: 1. Login to the {{%link href="https://console.developers.google.com/apis/credentials" %}}Google API Console{{%/link%}} and click **Create Project**. 2. Click **New Project**. <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} If you had already created a project in the Google developer console for your application, select your existing project. Skip the next step for an existing project.{{%/note%}} 3. Enter the required information and click **Create**. <br /> 4. After the project has been created, navigate to the **Credentials** page. You will be asked to configure the *OAuth consent screen* with your application details, if it is a new project. Click **Configure Consent Screen**. <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} If this is not a new project, you can modify some information about your application. Navigate to the {{%italics%}}OAuth consent screen{{%/italics%}} page. Click {{%bold%}}EDIT APP{{%/bold%}}, then follow the steps below.{{%/note%}} 5. Choose a user type for your app and click **Create**. <br /> 6. Provide the required information. <br /> 7. In the **App domain** section, under the *Application home page* section provide your applications home page. Enter the other information as required and click **Save And Continue**. <br /> 8. In the *Scopes* section, click **Edit**, if you wish to add or manage scopes other than the default section. <br /> 9. Select the scopes you require from the options listed. You can also manually provide the applicable scopes in the *Manually add scopes section*, and click **UPDATE**. Click **SAVE AND CONTINUE** once you have configured the scopes. <br /> 10. In the **Summary** section, confirm your configurations and click the **Edit** button should you need to edit any of the configuration. <br /> 11. Navigate back to the *Credentials* page and click **Create Credentials**. Select **OAuth client ID** from the drop-down list. <br /> 12. Select **Web application** as the type of your application your app is going to be from the drop-down selection of **Application type**. <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} Even if you host your application as an Android app, iOS, or a Flutter app, the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} to enable the social login will be the same, and can be obtained by choosing the application type as {{%bold%}}Web application{{%/bold%}}.{{%/note%}} * Enter the name of your application. <br /> * Click **ADD URI** under *Authorised JavaScript origins* and Click **ADD URI** under *Authorised redirect URIs* and enter the redirect URIs of your application in the following format: * {{%bold%}}https<span>://accounts.zohoportal.com/accounts/extoauth/ZAID/clientcallback{{%/bold%}} * {{%bold%}}https<span>://{{appdomain}}/accounts/pfs/ZAID/clientidpcallback{{%/bold%}}<br /> This URI can be copied from the Google Social Login pop-up, and steps to enable this URI is shown in this {{%link href="/en/cloud-scale/help/authentication/social-logins/introduction/#configure-authorized-uris" %}}help document{{%/link%}}:<br /><br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} The {{%badge%}}ZAID{{%/badge%}} value can be obtained from the {{%bold%}}Google Social Login{{%/bold%}} pop-up. However, to ensure that the Social Logins are enabled when you migrate your app to production, you need to reconfigure them using the {{%badge%}}Production ZAID{{%/badge%}}, and the appropriate app domain.{{%/note%}} <br /> Click **Create**, once you have added the required information. * You will now be directed to pop up displaying the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}}. You can copy the values and download the {{%badge%}}JSON{{%/badge%}} file containing the same. <br /> 13. Now, click the **Google** social login present in the Catalyst console and enter the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} you copied from the Google console, and click **Enable**. <br /> Your end users can now sign up to your application using their **Google** credentials. ### Enable Facebook Social Login To enable Facebook sign in option in your application you need to obtain the required **OAuth credentials** for your application from Facebook in the following manner: 1. Open the Facebook developer page: {{%link href="https://developers.facebook.com" %}}Meta Developer Console{{%/link%}} 2. Log in to Facebook, and click the **My Apps** option. <br /> 3. Click on **Create App** <br /> 4. Based on your requirement, you can choose to connect your business portfolio to the meta console. Since, this is not required to configure the social login, we click the relevant option and click **Next**. <br /> 5. Select the "**Authenticate and request data from users with Facebook Login**" and click **Next**. <br /> 6. Enter the required details and click **Next**. <br /> 7. Review your configurations and click **Create App**. <br /> 8. You will now be directed to the *Dashboard* of the Facebook developer console. Select the "**Customize adding a Facebook Login button**" option. <br /> You will be directed to the *Customization* section of the *Facebook Login*. <br /> 9. Click the **Settings** tab in the left-panel. <br /> 10. Scroll down to the *Client OAuth Settings* section. <br /> 11. In the **Valid OAuth Redirect URIs** input field section, provide the OAuth Redirect URIs in the following format: * **https<span></span>://accounts.zohoportal.com/accounts/extoauth/ZAID/clientcallback** * **https<span></span>://{{appdomain}}/accounts/pfs/ZAID/clientidpcallback** <br/> This URI can be copied from the Facebook Social Login pop-up, and steps to enable this URI is shown in this {{%link href="/en/cloud-scale/help/authentication/social-logins/introduction/#configure-authorized-uris" %}}help document{{%/link%}}: <br/> {{%note%}}{{%bold%}}Note:{{%/bold%}} The {{%badge%}}ZAID{{%/badge%}} value can be obtained from the {{%bold%}}Facebook Social Login{{%/bold%}} pop-up. However, to ensure that the Social Logins are enabled when you migrate your app to production, you need to reconfigure them using the {{%badge%}}Production ZAID{{%/badge%}}, and the appropriate app domain.{{%/note%}} <br/> Click **Save Changes**. 12. You will be directed back to the *Dashboard*. Now select the "**Basic**" option present in the *App Settings* section of the console, and copy and save the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} details generated by Facebook. Click **Save Changes** once you have completed reviewing the details. <br/> 18. You can now enable the **Facebook Social Login** in the console. Click the **Facebook** option and paste the **App ID** value in the {{%badge%}}Client ID{{%/badge%}} field and the **App Secret** value in the {{%badge%}}Client Secret{{%/badge%}} field, and click **Enable**. <br/> Your end users can will now be able to sign up to your application using their Facebook credentials. ### Enable LinkedIn Social Login To enable LinkedIn sign in option in your application you need to obtain the required **OAuth credentials** for your application from LinkedIn in the following manner: {{%note%}}{{%bold%}}Note:{{%/bold%}} * Before you implement the following steps, ensure you have created a {{%link href="https://www.linkedin.com/help/linkedin/answer/a543852/create-a-linkedin-page?lang=en" %}}LinkedIn page{{%/link%}} to represent your company or organization. This page is mandatory to configure LinkedIn social login. * LinkedIn uses {{%badge%}}{{%bold%}}OpenID Connect{{%/bold%}}{{%/badge%}} protocols and not {{%badge%}}{{%bold%}}OAuth{{%/badge%}}{{%/bold%}} protocols. For more information on this update, visit {{%link href="https://learn.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin-v2" %}}LinkedIn's documentation page{{%/link%}}{{%/note%}} 1. Login to the LinkedIn developer page: http://developer.linkedin.com 2. Click the **Create App** button in the center of the page. <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} You can also navigate to the {{%italics%}}My Apps{{%/italics%}} section present in the taskbar and click {{%bold%}}Create App{{%/bold%}}.{{%/note%}} 3. Enter the required information, such as the app name, privacy policy URL, and the app's logo. <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} If you have not created a LinkedIn page for your application, you can do so now by clicking the {{%link href="https://www.linkedin.com/help/linkedin/answer/a543852/create-a-linkedin-page?lang=en" %}}{{%bold%}}+Create a new LinkedIn Page{{%/bold%}}{{%/link%}} button.{{%/note%}} 4. Agree to the terms and conditions and click **Create app**. <br /> 5. Now verify your application by clicking the **Verify** button that appears next to your application's LinkedIn page. <br /> * Click **Generate URL** to generate verification URL. <br /> * Complete the verification process, and click **I'm done**. <br /> 6. In the *Settings* section, add your application URL to the *Domain* input field of the **Widgets** section if necessary. <br /> 7. Navigate to the *Products* tab, select "**Sign in with LinkedIn Using OpenID Connect**", and click **Request Access**. <br /> Read and accept the terms and conditions, click the **Request Access** button to allow sign ups with LinkedIn using {{%badge%}}OpenID connect{{%/badge%}}. <br /> 8. Click the **Auth tab**, and copy the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} present in the Authentication keys section. In the **OAuth 2.0** scopes section you will be able to view three scopes have been added: * {{%badge%}}openid{{%/badge%}} * {{%badge%}}profile{{%/badge%}} * {{%badge%}}email{{%/badge%}} <br /> 9. Now click the *Auth tab*, and copy the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} present in the *Authentication keys* section. In the *Auth 2.0 settings* section add **Authorized Redirection URLs** of your application in the following format: * {{%bold%}}https<span>://accounts.zohoportal.com/accounts/extoauth/ZAID/clientcallback{{%/bold%}} * {{%bold%}}https<span>://{{appdomain}}/accounts/pfs/ZAID/clientidpcallback{{%/bold%}}<br /> This URI can be copied from the LinkedIn Social Login pop-up, and steps to enable this URI is shown in this {{%link href="/en/cloud-scale/help/authentication/social-logins/introduction/#configure-authorized-uris" %}}help document{{%/link%}}:<br /><br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} The {{%badge%}}ZAID{{%/badge%}} value can be obtained from the {{%bold%}}LinkedIn Social Login{{%/bold%}} pop-up. However, to ensure that the Social Logins are enabled when you migrate your app to production, you need to reconfigure them using the {{%badge%}}Production ZAID{{%/badge%}}, and the appropriate app domain.{{%/note%}} <br /> 10. Click the **LinkedIn Social Login** option present in the console, and add the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} obtained. Then, click **Enable**. <br /> Your end users can now sign up to your application using their LinkedIn credentials. ### Enable Microsoft 365 Social Login To enable **Microsoft 365** sign in option in your application you will need to obtain the requisite **OAuth credentials** for your application with Microsoft Azure in the following manner: 1. Open {{%link href="https://login.microsoftonline.com/common/oauth2/authorize?resource=https%3a%2f%2fmanagement.core.windows.net%2f&response_mode=form_post&response_type=code%2Bid_token&scope=user_impersonation%2Bopenid&state=OpenIdConnect.AuthenticationProperties%3dBfkwHFJ3Egk92KL8DPHN2-RQjP-h_WwVeILIb8XOeiHICZaVr0nG2-yhM_KcVOmT_8fXBwSbnsYJwBG_EoCgAkuxqj9DQYKycadknX5B1H3zrlC5ZweOVaj0jaNFa83WvK8h8EetcYOBsZODvR81D0WlMn4etuNsZss49RYPT83fjHN6fopQee6PTqF0_2F6BooYsnCo-xkZu_msvizJsCf3syueh-NhcznRUENLcQK1ri7lLfT16wWqixbKO6cRFVIY6bwUxAsWts8rJM58JA&nonce=637021409072386485.M2Q0NzQ4MGYtM2EzNy00ODlhLWI4NjYtNTc3MmM5ZGJlN2NhN2RjNGUwMWUtYzdkYS00OTQzLWI1MjYtNTM5NzJjODA0ODlk&client_id=c44b4083-3bb0-49c1-b47d-974e53cbdf3c&redirect_uri=https%3a%2f%2fportal.azure.com%2fsignin%2findex%2f%3ffeature.refreshtokenbinding%3dtrue&site_id=501430&client-request-id=e67688f1-801d-41b0-b748-db616b4b7b06&x-client-SKU=ID_NET&x-client-ver=1.0.40306.1554" %}}Microsoft Azure{{%/link%}} and login to the console. <br /> 2. Navigate to the menu section of the console and click **App Registrations**. <br /> 3. Click **New Registration**. <br /> 4. Enter the application name, choose the required permission. In the **Redirect URI** section, choose **Web** and enter the URI in the following format:<br />{{%bold%}}https<span>://{{appdomain}}/accounts/pfs/ZAID/clientidpcallback{{%/bold%}}<br /> This URI can be copied from the Microsoft 365 Social Login pop-up, and steps to enable this URI is shown in this {{%link href="/en/cloud-scale/help/authentication/social-logins/introduction/#configure-authorized-uris" %}}help document{{%/link%}}:<br /><br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} The {{%badge%}}ZAID{{%/badge%}} value can be obtained from the {{%bold%}}Microsoft 365 Social Login{{%/bold%}} pop-up. However, to ensure that the Social Logins are enabled when you migrate your app to production, you need to reconfigure them using the {{%badge%}}Production ZAID{{%/badge%}}, and the appropriate app domain.{{%/note%}} <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} You will have to add the second URI in a later step.{{%/note%}} 5. You will now be directed to the *Overview* section. Here you can copy the Application ID ({{%badge%}}Client ID{{%/badge%}}). <br /> 6. Click the **Redirect URIs** section. <br /> * In the *Redirect URI* section, click **Add URI** and add the second URI in the following format:{{%bold%}}https<span></span>://accounts.zohoportal.com/accounts/extoauth/ZAID/clientcallback{{%/bold%}}<br /> <br /> {{%note%}}{{%bold%}}Note:{{%/bold%}} The {{%badge%}}ZAID{{%/badge%}} value can be obtained from the {{%bold%}}Microsoft 365 Social Login{{%/bold%}} pop-up. However, to ensure that the Social Logins are enabled when you migrate your app to production, you need to reconfigure them using the {{%badge%}}Production ZAID{{%/badge%}}, and the appropriate app domain.{{%/note%}} 7. Now, navigate to the **Certificates & secrets** section from the menu-bar, and click the *Client secrets* section. <br /> 8. Click **New Client Secret**, to generate {{%badge%}}Client Secret{{%/badge%}}. <br /> 9. Enter the required details and click **Add**. <br /> 10. Copy the key present under the ({{%badge%}}Value{{%/badge%}}) section. <br /> 11. Click the **Microsoft 365 Social Login** option present in the console and add the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} obtained and click **Enable**. <br /> -------------------------------------------------------------------------------- title: "Modifying the Social Logins" description: "Catalyst Authentication enables you to provide secure authentication and sign-ins for your app users, and manage their user accounts." last_updated: "2026-03-18T07:41:08.537Z" source: "https://docs.catalyst.zoho.com/en/cloud-scale/help/authentication/social-logins/modifying-social-logins/" service: "Cloud Scale" -------------------------------------------------------------------------------- # Modifying the Social Logins Once you have configured the Social Logins, you will be able to modify, disable and delete them in the {{%link href="/en/cloud-scale/help/authentication/authentication-types/" %}}*Authentication Types*{{%/link%}} section. <br /> ### Updating the Social Login To update the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}}: 1. Click the icon of the social login you wish to update. <br /> 2. Click the ellipsis icon and choose the **Edit** option. <br /> 3. Make the necessary changes and click **Update**. <br /> ### Disable a Social Login You can temporarily disable a social login from your authentication element. After you disable a social login, the end-users will not be able to sign up/sign in using the disabled social login option. However, the values of the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} will still be stored with Catalyst. {{%note%}}{{%bold%}}Note:{{%/bold%}} If you choose to enable a social login again at some point, you can simply re-enable it here without having to re-configure the OAuth credentials, and it will be active once again.{{%/note%}} To disable a social login, click the icon of the social login you wish to disable: 1. Click the ellipsis icon and select **Disable**. <br /> 2. Click **Yes, Proceed**. <br /> The social login will be disabled. To re-enable a social login, click the icon of the disabled social login and click **Enable**. <br /> ### Delete a Social Login After you delete a social login, the end-users will not be able to sign up/sign in using the deleted social login option. The values of the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} will be permanently deleted from the Catalyst console. To delete a social login, click the icon of the social login you wish to delete: 1. Click the ellipsis icon and select **Delete**. <br /> 2. Click **Yes, Proceed**. <br /> The social login will be deleted from your login element. You will have to re-enter the {{%badge%}}Client ID{{%/badge%}} and {{%badge%}}Client Secret{{%/badge%}} to enable the social login again.