{"data":{"id":"740501","string_id":"WU3RiBAI","status":"1","parent_id":"740398","slug":"authentication-configuration","order":"7","name":"Authentication Configuration","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"0","add_time":"1773213849","update_time":"1777282125","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"parent_name":"User Guide","parent_type":"1","parent_slug":"user-guide","child":[{"id":"740502","string_id":"rcngMc1G","status":"1","parent_id":"740501","slug":"authentication-providers-google","order":"0","name":"Google","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"RootAuth Providers: Google Social Login & OAuth Setup Guide","seo_keyword":"Social Login, Google Login, OAuth Configuration, Custom Credentials, Redirect URI","seo_desc":"Integrate Google login with RootAuth. Step-by-step guide on applying for Google OAuth credentials, choosing shared\/custom types, configuration, and end-user experience.","share_switch":"0","share_code":"","author":"","published_time":"1773215017","add_time":"1773213853","update_time":"1780898135","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"3","file_type":"","auth_id":"[\"740502\", \"740501\", \"740398\"]","content":{"content_id":"740502","content":"

By configuring social login providers, your application users can conveniently log in or register using their own Google accounts without needing to remember additional passwords. RootAuth currently supports Google login and provides two configuration methods: Shared Credentials (for testing) and Custom Credentials (for production environments).<\/p>\n

Path:<\/strong> Log in to the RootAuth console → Navigate to the target application → Click Configuration in the top navigation bar → Select Application Management – Authentication Configuration → Choose Providers<\/p>\n

<\/h2>\n
1. Feature Overview<\/h2>\n
RootAuth's social login feature enables you to quickly integrate Google account login, enhancing the user experience. The system provides two configuration methods:<\/p>\n
\n
\n
Shared RootAuth Credentials:<\/strong> No need to apply for OAuth credentials yourself; can be used directly for testing to quickly experience the Google login process.<\/p>\n<\/li>\n
\n
Custom Credentials:<\/strong> You need to go to the Google Cloud Console to apply for your own OAuth Client ID and Secret. Suitable for production environments, providing full brand control and higher security.<\/p>\n<\/li>\n<\/ul>\n
<\/h2>\n
2. Applying for a Google OAuth Client Account<\/h2>\n
To integrate Google login into your application, you first need to create an OAuth 2.0 client in the Google Cloud Console. Follow the steps below (skip if you are already familiar).<\/p>\n
Step 1: Access the Google Cloud Console<\/h3>\n
Open the Google Cloud Console<\/a> and log in with your Google account. If you don't have an account, please register first.<\/p>\n
Step 2: Create or Select a Project<\/h3>\n
At the top of the console, click the project dropdown menu. Select an existing project or click \"New Project\" to create a new one, filling in the project name and other information. Ensure the current context is the project you intend to use.<\/p>\n
Step 3: Navigate to \"APIs & Services\" > \"Credentials\"<\/h3>\n
In the left navigation menu, select \"APIs & Services\"<\/strong>, then click \"Credentials\"<\/strong>.<\/p>\n
Step 4: Configure the OAuth Consent Screen (If First Time Use)<\/h3>\n
On the \"Credentials\" page, if prompted to \"Configure Consent Screen\", click it. If it indicates that the Google Auth Platform is not yet configured, click \"Get Started\".<\/p>\n
You will enter the project configuration page. Fill in the necessary information, such as:<\/p>\n
\n
\n
App name<\/strong><\/p>\n<\/li>\n
\n
User support email<\/strong><\/p>\n<\/li>\n
\n
Audience<\/strong> (select \"External\" for general applications)<\/p>\n<\/li>\n
\n
Developer contact information<\/strong><\/p>\n<\/li>\n<\/ul>\n
Then click \"Create\"<\/strong>.<\/p>\n
Step 5: Create an OAuth Client<\/h3>\n
On the \"Overview\" page, click \"Create OAuth Client ID\"<\/strong> and configure the relevant information.<\/p>\n
The system will prompt you to select an application type. For most web applications, choose \"Web Application\"<\/strong> and fill in the following information:<\/p>\n
\n
\n
Name:<\/strong> Give your client an easily identifiable name, e.g., \"My Application - Web\".<\/p>\n<\/li>\n
\n
Authorized JavaScript origins:<\/strong> Add your application's frontend domain (e.g., `https:\/\/yourdomain.com<\/code>) and local development addresses (e.g., http:\/\/localhost:3000<\/code>). This helps prevent cross-site request forgery.<\/p>\n<\/li>\n`
\nAuthorized redirect URIs:<\/strong> This is the address Google redirects to after user authorization. You need to fill in the redirect URI obtained from the RootAuth console. Ensure this is entered accurately; otherwise, the authorization flow will fail.<\/p>\n<\/li>\n<\/ul>\n Step 6: Create and Obtain Credentials<\/h3>\nClick the \"Create\"<\/strong> button. A popup will immediately display your Client ID<\/strong> and Client Secret<\/strong>. Be sure to copy and securely store these two values<\/strong>; you will need to enter them in the RootAuth console later.<\/p>\n \n\nClient ID:<\/strong> Used to identify your application; it is the application's public identifier.<\/p>\n<\/li>\n \nClient Secret:<\/strong> Equivalent to a password. Do not disclose it. If accidentally lost, you can regenerate it in the credentials list at any time.<\/p>\n<\/li>\n<\/ul>\n Step 7: Next Steps<\/h3>\nReturn to the RootAuth console. In Authentication Management → Providers → Google Configuration<\/strong>, fill in the Client ID and Client Secret obtained above, and ensure the redirect URI matches the one you entered in the Google Cloud Console.<\/p>\n \nTip:<\/strong> If you haven't completed the configuration in RootAuth yet, you can leave it blank for now and edit the client later. However, it is recommended to have it ready in advance.<\/p>\n<\/blockquote>\n <\/h2>\n3. Configuring Google Login<\/h2>\n 3.1 Enabling Google Login<\/h3>\nFind Google<\/strong> in the providers list and click the \"Enable\"<\/strong> button on the right. A configuration popup will appear. There is a toggle switch in the upper-left corner of the popup, which is off by default. Click to turn it \"On\"<\/strong>; the credential type options below will become selectable.<\/p>\n <\/p>\n 3.2 Selecting a Credential Type<\/h3>\nThe popup provides two credential types; you need to choose one:<\/p>\n \n\nShared RootAuth Credentials<\/strong><\/p>\n \n\nDescription:<\/strong> Test Google OAuth without any setup.<\/p>\n<\/li>\n \nApplicable Scenario:<\/strong> Development testing, quick validation.<\/p>\n<\/li>\n \nAction:<\/strong> After selecting this card, simply click the \"Save\"<\/strong> button in the lower-right corner of the popup for it to take effect.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n <\/p>\n \n\nCustom Credentials<\/strong><\/p>\n \n\nDescription:<\/strong> Configure your own Google OAuth for production environments.<\/p>\n<\/li>\n \nApplicable Scenario:<\/strong> Official launch; requires you to apply for Google OAuth credentials yourself.<\/p>\n<\/li>\n \nAction:<\/strong> After selecting this card, a detailed configuration form will expand below. Complete the form before saving.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n <\/p>\n Custom Credentials Form Field Descriptions<\/strong><\/p>\n \n\n\n\n\n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n Required<\/th>\n<\/tr>\n<\/thead>\n Google Client ID<\/strong><\/td>\n The Client ID you generated in the Google Cloud Console<\/td>\n Yes<\/td>\n<\/tr>\n Google Client Secret<\/strong><\/td>\n The corresponding Client Secret; input is masked<\/td>\n Yes<\/td>\n<\/tr>\n Authorized Redirect URI<\/strong><\/td>\n Automatically generated by the system. You need to copy this URI and fill it in as a callback address in the Google Cloud Console<\/td>\n Read-only<\/td>\n<\/tr>\n Authorization Scope<\/strong><\/td>\n Fixed as email, profile, openid<\/code>; no modification needed<\/td>\n Read-only<\/td>\n<\/tr>\n Login Mode<\/strong><\/td>\n Fixed as \"Available for login\/registration\", meaning users can log in or register via Google<\/td>\n Checked by default, cannot be modified<\/td>\n<\/tr>\n Account Linking<\/strong><\/td>\n If the email used for Google login matches an existing account email in the system, it is automatically linked; otherwise, a new account is created<\/td>\n Checked by default, cannot be modified<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n\nNote:<\/strong> When filling in the Client ID and Secret, the system does not validate their format or validity. Actual verification occurs during the OAuth flow when a user logs in with Google for the first time.<\/p>\n<\/blockquote>\n 3.3 Saving the Configuration<\/h3>\nAfter making your selection or filling in the form, click the \"Save\"<\/strong> button in the lower-right corner of the popup. Upon successful saving, the popup closes, and the status for Google in the providers list changes to \"Enabled\"<\/strong>. If you selected Custom Credentials, it will be tagged as \"Custom Credentials\"<\/strong>, and the button on the right will change to \"Manage\"<\/strong>.<\/p>\n <\/h2>\n4. Managing an Enabled Configuration<\/h2>\nClick the \"Manage\"<\/strong> button next to Google to reopen the configuration popup.<\/p>\n The popup will fully load the configuration state you last saved (toggle state, selected credential type, and any custom information entered).<\/p>\n You can modify the configuration within the popup (e.g., switch credential types, update custom credential fields). After making changes, click \"Save\"<\/strong> for them to take effect.<\/p>\n To disable Google login, turn off the toggle switch at the top of the popup and click \"Save\"<\/strong>. Once disabled, the Google button will no longer be displayed on the end-user login page.<\/p>\n \nNote:<\/strong> After disabling Google login, any previously entered custom credential information is retained, so you won't need to re-enter it if you enable it again later.<\/p>\n<\/blockquote>\n <\/h2>\n5. End-User Experience<\/h2>\nOnce the configuration takes effect, a Google login button<\/strong> will automatically appear on your application's login and registration pages. You can preview the effect via Application – Application Management – Try Registration\/Login<\/strong> in the upper-right corner. When users click this button, they will be redirected to the Google authorization page; after consenting, they can quickly log in or register.<\/p>\n \n\nIf the email used for Google login already exists in your application's user pool, the system will automatically link the accounts.<\/p>\n<\/li>\n \nOtherwise, a new user account will be created automatically.<\/p>\n<\/li>\n<\/ul>\n <\/p>\n \nNote on Caching:<\/strong> Due to possible browser or CDN caching, it may take up to 2 minutes for configuration changes to be fully effective for all end-users. If a user clicks the old button and encounters a prompt, refreshing the page should load the latest configuration.<\/p>\n<\/blockquote>\n <\/h2>\n6. Viewing a User's Linked Google Account<\/h2>\nIn the User Management → User Details<\/strong> page of your application, within the \"Authentication Methods\"<\/strong> section, you can view information about the user's linked Google account:<\/p>\n \n\nGoogle icon and name<\/p>\n<\/li>\n \nLinked Google email address<\/p>\n<\/li>\n \nTime of the last login using Google<\/p>\n<\/li>\n<\/ul>\n Currently, this information is for display purposes only; manual unlinking is not supported.<\/p>\n <\/p>","pure_content":"By configuring social login providers, your application users can conveniently log in or register using their own Google accounts without needing to remember additional passwords. RootAuth currently supports Google login and provides two configuration methods: Shared Credentials (for testing) and Custom Credentials (for production environments).\nPath:\u00a0Log in to the RootAuth console \u2192 Navigate to the target application \u2192 Click\u00a0Configuration\u00a0in the top navigation bar \u2192 Select\u00a0Application Management \u2013 Authentication Configuration\u00a0\u2192 Choose\u00a0Providers\n\u00a0\n1. Feature Overview\nRootAuth's social login feature enables you to quickly integrate Google account login, enhancing the user experience. The system provides two configuration methods:\n\n\nShared RootAuth Credentials:\u00a0No need to apply for OAuth credentials yourself; can be used directly for testing to quickly experience the Google login process.\n\n\nCustom Credentials:\u00a0You need to go to the Google Cloud Console to apply for your own OAuth Client ID and Secret. Suitable for production environments, providing full brand control and higher security.\n\n\n\u00a0\n2. Applying for a Google OAuth Client Account\nTo integrate Google login into your application, you first need to create an OAuth 2.0 client in the Google Cloud Console. Follow the steps below (skip if you are already familiar).\nStep 1: Access the Google Cloud Console\nOpen the\u00a0Google Cloud Console\u00a0and log in with your Google account. If you don't have an account, please register first.\nStep 2: Create or Select a Project\nAt the top of the console, click the project dropdown menu. Select an existing project or click \"New Project\" to create a new one, filling in the project name and other information. Ensure the current context is the project you intend to use.\nStep 3: Navigate to \"APIs & Services\" > \"Credentials\"\nIn the left navigation menu, select\u00a0\"APIs & Services\", then click\u00a0\"Credentials\".\nStep 4: Configure the OAuth Consent Screen (If First Time Use)\nOn the \"Credentials\" page, if prompted to \"Configure Consent Screen\", click it. If it indicates that the Google Auth Platform is not yet configured, click \"Get Started\".\nYou will enter the project configuration page. Fill in the necessary information, such as:\n\n\nApp name\n\n\nUser support email\n\n\nAudience\u00a0(select \"External\" for general applications)\n\n\nDeveloper contact information\n\n\nThen click\u00a0\"Create\".\nStep 5: Create an OAuth Client\nOn the \"Overview\" page, click\u00a0\"Create OAuth Client ID\"\u00a0and configure the relevant information.\nThe system will prompt you to select an application type. For most web applications, choose\u00a0\"Web Application\"\u00a0and fill in the following information:\n\n\nName:\u00a0Give your client an easily identifiable name, e.g., \"My Application - Web\".\n\n\nAuthorized JavaScript origins:\u00a0Add your application's frontend domain (e.g.,\u00a0https:\/\/yourdomain.com) and local development addresses (e.g.,\u00a0http:\/\/localhost:3000). This helps prevent cross-site request forgery.\n\n\nAuthorized redirect URIs:\u00a0This is the address Google redirects to after user authorization. You need to fill in the redirect URI obtained from the RootAuth console. Ensure this is entered accurately; otherwise, the authorization flow will fail.\n\n\nStep 6: Create and Obtain Credentials\nClick the\u00a0\"Create\"\u00a0button. A popup will immediately display your\u00a0Client ID\u00a0and\u00a0Client Secret.\u00a0Be sure to copy and securely store these two values; you will need to enter them in the RootAuth console later.\n\n\nClient ID:\u00a0Used to identify your application; it is the application's public identifier.\n\n\nClient Secret:\u00a0Equivalent to a password. Do not disclose it. If accidentally lost, you can regenerate it in the credentials list at any time.\n\n\nStep 7: Next Steps\nReturn to the RootAuth console. In\u00a0Authentication Management \u2192 Providers \u2192 Google Configuration, fill in the Client ID and Client Secret obtained above, and ensure the redirect URI matches the one you entered in the Google Cloud Console.\n\nTip:\u00a0If you haven't completed the configuration in RootAuth yet, you can leave it blank for now and edit the client later. However, it is recommended to have it ready in advance.\n\n\u00a0\n3. Configuring Google Login\n3.1 Enabling Google Login\nFind\u00a0Google\u00a0in the providers list and click the\u00a0\"Enable\"\u00a0button on the right. A configuration popup will appear. There is a toggle switch in the upper-left corner of the popup, which is off by default. Click to turn it\u00a0\"On\"; the credential type options below will become selectable.\n\n3.2 Selecting a Credential Type\nThe popup provides two credential types; you need to choose one:\n\n\nShared RootAuth Credentials\n\n\nDescription:\u00a0Test Google OAuth without any setup.\n\n\nApplicable Scenario:\u00a0Development testing, quick validation.\n\n\nAction:\u00a0After selecting this card, simply click the\u00a0\"Save\"\u00a0button in the lower-right corner of the popup for it to take effect.\n\n\n\n\n\n\n\nCustom Credentials\n\n\nDescription:\u00a0Configure your own Google OAuth for production environments.\n\n\nApplicable Scenario:\u00a0Official launch; requires you to apply for Google OAuth credentials yourself.\n\n\nAction:\u00a0After selecting this card, a detailed configuration form will expand below. Complete the form before saving.\n\n\n\n\n\nCustom Credentials Form Field Descriptions\n\n\n\n\n Field\n Description\n Required\n\n\n\n\n Google Client ID\n The Client ID you generated in the Google Cloud Console\n Yes\n\n\n Google Client Secret\n The corresponding Client Secret; input is masked\n Yes\n\n\n Authorized Redirect URI\n Automatically generated by the system. You need to copy this URI and fill it in as a callback address in the Google Cloud Console\n Read-only\n\n\n Authorization Scope\n Fixed as\u00a0email, profile, openid; no modification needed\n Read-only\n\n\n Login Mode\n Fixed as \"Available for login\/registration\", meaning users can log in or register via Google\n Checked by default, cannot be modified\n\n\n Account Linking\n If the email used for Google login matches an existing account email in the system, it is automatically linked; otherwise, a new account is created\n Checked by default, cannot be modified\n\n\n\n\n\nNote:\u00a0When filling in the Client ID and Secret, the system does not validate their format or validity. Actual verification occurs during the OAuth flow when a user logs in with Google for the first time.\n\n3.3 Saving the Configuration\nAfter making your selection or filling in the form, click the\u00a0\"Save\"\u00a0button in the lower-right corner of the popup. Upon successful saving, the popup closes, and the status for Google in the providers list changes to\u00a0\"Enabled\". If you selected Custom Credentials, it will be tagged as\u00a0\"Custom Credentials\", and the button on the right will change to\u00a0\"Manage\".\n\u00a0\n4. Managing an Enabled Configuration\nClick the\u00a0\"Manage\"\u00a0button next to Google to reopen the configuration popup.\nThe popup will fully load the configuration state you last saved (toggle state, selected credential type, and any custom information entered).\nYou can modify the configuration within the popup (e.g., switch credential types, update custom credential fields). After making changes, click\u00a0\"Save\"\u00a0for them to take effect.\nTo disable Google login, turn off the toggle switch at the top of the popup and click\u00a0\"Save\". Once disabled, the Google button will no longer be displayed on the end-user login page.\n\nNote:\u00a0After disabling Google login, any previously entered custom credential information is retained, so you won't need to re-enter it if you enable it again later.\n\n\u00a0\n5. End-User Experience\nOnce the configuration takes effect, a\u00a0Google login button\u00a0will automatically appear on your application's login and registration pages. You can preview the effect via\u00a0Application \u2013 Application Management \u2013 Try Registration\/Login\u00a0in the upper-right corner. When users click this button, they will be redirected to the Google authorization page; after consenting, they can quickly log in or register.\n\n\nIf the email used for Google login already exists in your application's user pool, the system will automatically link the accounts.\n\n\nOtherwise, a new user account will be created automatically.\n\n\n\n\nNote on Caching:\u00a0Due to possible browser or CDN caching, it may take up to 2 minutes for configuration changes to be fully effective for all end-users. If a user clicks the old button and encounters a prompt, refreshing the page should load the latest configuration.\n\n\u00a0\n6. Viewing a User's Linked Google Account\nIn the\u00a0User Management \u2192 User Details\u00a0page of your application, within the\u00a0\"Authentication Methods\"\u00a0section, you can view information about the user's linked Google account:\n\n\nGoogle icon and name\n\n\nLinked Google email address\n\n\nTime of the last login using Google\n\n\nCurrently, this information is for display purposes only; manual unlinking is not supported.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1773213853","update_time":"1779161827"},"pure_content":"By configuring social login providers, your application users can conveniently log in or register using their own Google accounts without needing to remember additional passwords. RootAuth currently s"},{"id":"810170","string_id":"vFUe6I78","status":"1","parent_id":"740501","slug":"authentication-providers-telegram","order":"0","name":"Telegram","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Telegram Login Configuration Guide","seo_keyword":"Telegram login, Telegram OAuth, social login, RootAuth, passwordless login","seo_desc":"Learn how to configure Telegram login in RootAuth so users can sign in or sign up through Telegram authorization and view authentication records.","share_switch":"0","share_code":"","author":"","published_time":"1780899971","add_time":"1780898187","update_time":"1780975887","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"3","file_type":"","auth_id":"[\"810170\", \"740501\", \"740398\"]","content":{"content_id":"810170","content":" RootAuth supports Telegram login. After it is enabled, users can select Telegram<\/strong> on the login or sign-up page and complete authentication through Telegram without entering a password.<\/p>\n Path<\/strong>: Log in to the RootAuth console → open the target application → click Configuration<\/strong> in the top navigation bar → Application Management - Authentication Configuration<\/strong> → select Providers<\/strong><\/p>\n <\/p>\n 1. Before You Start<\/h2>\nBefore configuring Telegram login, make sure you have completed the following:<\/p>\n \nYou have a Telegram account.<\/li>\n You have contacted @BotFather<\/code> in Telegram and created a bot.<\/li>\n You have configured the Web Login domain for the bot in @BotFather<\/code>.<\/li>\n You have obtained the Client ID and Client Secret from Telegram.<\/li>\n<\/ol>\n\nTelegram verifies the authorization domain. Make sure the domain configured in BotFather matches the domain of the callback URL shown in RootAuth.<\/p>\n<\/blockquote>\n <\/p>\n 2. Enable Telegram in RootAuth<\/h2>\nIn the provider list, find Telegram<\/strong> and click Enable<\/strong>.<\/p>\n In the configuration dialog, turn on Telegram login and fill in the following information:<\/p>\n \n\n\n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n Client ID<\/strong><\/td>\n Obtained from Telegram BotFather<\/td>\n<\/tr>\n Client Secret<\/strong><\/td>\n Obtained from Telegram BotFather<\/td>\n<\/tr>\n Callback URL<\/strong><\/td>\n Generated by RootAuth. Copy it and configure it in Telegram BotFather.<\/td>\n<\/tr>\n Login mode<\/strong><\/td>\n Used for login and sign-up by default<\/td>\n<\/tr>\n Account binding<\/strong><\/td>\n Automatically links accounts with the same Telegram ID by default<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nAfter completing the fields, click Save<\/strong>.<\/p>\n After the configuration is saved, Telegram is shown as Enabled<\/strong>, and the action button changes to Manage<\/strong>. To update the configuration later, click Manage<\/strong>.<\/p>\n <\/p>\n <\/p>\n <\/h2>\n3. How Users Log In with Telegram<\/h2>\nAfter Telegram login is enabled, the login or sign-up page displays a Telegram login button.<\/p>\n When a user clicks Telegram<\/strong>, they are taken through Telegram's official authorization flow. Depending on the user's current Telegram session, Telegram may show an authorization dialog or redirect the user to an authorization page.<\/p>\n After the user confirms authorization, RootAuth automatically completes the following steps:<\/p>\n \nReceives the user's public information returned by Telegram.<\/li>\n Checks whether an existing account matches the Telegram ID.<\/li>\n If an account already exists, logs the user in directly.<\/li>\n If no account exists, creates a new account and completes login.<\/li>\n<\/ol>\n<\/p>\n <\/h2>\n 4. View a User's Telegram Authentication Method<\/h2>\nAfter a user logs in or signs up with Telegram, you can view the authentication record in the user details.<\/p>\n Go to User Management<\/strong>, open the target user's details, and check the Authentication Methods<\/strong> section.<\/p>\n The Telegram authentication method displays:<\/p>\n \n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n Authentication method<\/td>\n Telegram<\/td>\n<\/tr>\n Identifier<\/td>\n Telegram ID<\/td>\n<\/tr>\n Last used<\/td>\n The most recent time the user logged in with Telegram<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\n \nIf the application unbinds the user's Telegram account through the API, this authentication method is removed from the user details.<\/p>\n<\/blockquote>\n <\/p>\n 5. Integration Options<\/h2>\nTelegram login supports two integration options:<\/p>\n \n\n\n\n\n\nIntegration option<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n Hosted<\/td>\n Use the login and sign-up pages hosted by RootAuth. After Telegram is enabled, the Telegram login button is displayed automatically.<\/td>\n<\/tr>\n API<\/td>\n Build your own Telegram login entry in your application, then use APIs to complete login, binding, or unbinding.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nFor integration details, see the Developer Integration documentation<\/a>.<\/strong><\/p>\n <\/p>\n 6. Disable Telegram Login<\/h2>\nTo disable Telegram login, open the Telegram management dialog, turn off the switch, and save the configuration.<\/p>\n After Telegram login is disabled:<\/p>\n \nThe Telegram login button is no longer shown on the login or sign-up page.<\/li>\n The saved Telegram configuration is retained.<\/li>\n Existing users' Telegram binding records are not deleted.<\/li>\n<\/ol>\n<\/p>","pure_content":"RootAuth supports Telegram login. After it is enabled, users can select Telegram on the login or sign-up page and complete authentication through Telegram without entering a password.\nPath: Log in to the RootAuth console \u2192 open the target application \u2192 click Configuration in the top navigation bar \u2192 Application Management - Authentication Configuration \u2192 select Providers\n\u00a0\n1. Before You Start\nBefore configuring Telegram login, make sure you have completed the following:\n\nYou have a Telegram account.\nYou have contacted @BotFather in Telegram and created a bot.\nYou have configured the Web Login domain for the bot in @BotFather.\nYou have obtained the Client ID and Client Secret from Telegram.\n\n\nTelegram verifies the authorization domain. Make sure the domain configured in BotFather matches the domain of the callback URL shown in RootAuth.\n\n\u00a0\n2. Enable Telegram in RootAuth\nIn the provider list, find Telegram and click Enable.\nIn the configuration dialog, turn on Telegram login and fill in the following information:\n\n\n\n Field\n Description\n\n\n\n\n Client ID\n Obtained from Telegram BotFather\n\n\n Client Secret\n Obtained from Telegram BotFather\n\n\n Callback URL\n Generated by RootAuth. Copy it and configure it in Telegram BotFather.\n\n\n Login mode\n Used for login and sign-up by default\n\n\n Account binding\n Automatically links accounts with the same Telegram ID by default\n\n\n\nAfter completing the fields, click Save.\nAfter the configuration is saved, Telegram is shown as Enabled, and the action button changes to Manage. To update the configuration later, click Manage.\n\n\n\u00a0\n3. How Users Log In with Telegram\nAfter Telegram login is enabled, the login or sign-up page displays a Telegram login button.\nWhen a user clicks Telegram, they are taken through Telegram's official authorization flow. Depending on the user's current Telegram session, Telegram may show an authorization dialog or redirect the user to an authorization page.\nAfter the user confirms authorization, RootAuth automatically completes the following steps:\n\nReceives the user's public information returned by Telegram.\nChecks whether an existing account matches the Telegram ID.\nIf an account already exists, logs the user in directly.\nIf no account exists, creates a new account and completes login.\n\n\n\u00a0\n4. View a User's Telegram Authentication Method\nAfter a user logs in or signs up with Telegram, you can view the authentication record in the user details.\nGo to User Management, open the target user's details, and check the Authentication Methods section.\nThe Telegram authentication method displays:\n\n\n\n Field\n Description\n\n\n\n\n Authentication method\n Telegram\n\n\n Identifier\n Telegram ID\n\n\n Last used\n The most recent time the user logged in with Telegram\n\n\n\n\n\nIf the application unbinds the user's Telegram account through the API, this authentication method is removed from the user details.\n\n\u00a0\n5. Integration Options\nTelegram login supports two integration options:\n\n\n\n Integration option\n Description\n\n\n\n\n Hosted\n Use the login and sign-up pages hosted by RootAuth. After Telegram is enabled, the Telegram login button is displayed automatically.\n\n\n API\n Build your own Telegram login entry in your application, then use APIs to complete login, binding, or unbinding.\n\n\n\nFor integration details, see the Developer Integration documentation.\n\u00a0\n6. Disable Telegram Login\nTo disable Telegram login, open the Telegram management dialog, turn off the switch, and save the configuration.\nAfter Telegram login is disabled:\n\nThe Telegram login button is no longer shown on the login or sign-up page.\nThe saved Telegram configuration is retained.\nExisting users' Telegram binding records are not deleted.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1780898187","update_time":"1780975886"},"pure_content":"RootAuth supports Telegram login. After it is enabled, users can select Telegram on the login or sign-up page and complete authentication through Telegram without entering a password.\nPath: Log in to"},{"id":"810172","string_id":"QjFwOb7c","status":"1","parent_id":"740501","slug":"authentication-providers-facebook","order":"0","name":"Facebook","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Facebook Login Configuration Guide","seo_keyword":"Facebook login, Facebook OAuth, social login, RootAuth, account binding","seo_desc":"Learn how to configure Facebook login in RootAuth, enable Facebook OAuth with custom credentials, and manage account binding and authentication records.","share_switch":"0","share_code":"","author":"","published_time":"1780899973","add_time":"1780898290","update_time":"1780976131","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"3","file_type":"","auth_id":"[\"810172\", \"740501\", \"740398\"]","content":{"content_id":"810172","content":" RootAuth supports Facebook login. After it is enabled, users can select Facebook<\/strong> on the login or sign-up page and complete login or registration through Facebook authorization.<\/p>\n Path<\/strong>: Log in to the RootAuth console → open the target application → click Configuration<\/strong> in the top navigation bar → Application Management - Authentication Configuration<\/strong> → select Providers<\/strong><\/p>\n <\/p>\n 1. Before You Start<\/h2>\nBefore configuring Facebook login, make sure you have completed the following:<\/p>\n \nYou have a Facebook developer account.<\/li>\n You have created an app in the Facebook developer platform.<\/li>\n You have obtained the Facebook App ID and App Secret.<\/li>\n You have prepared your application domain for configuring the OAuth redirect URI.<\/li>\n<\/ol>\n\nFacebook verifies the OAuth redirect URI. Make sure the callback URL configured in the Facebook app matches the Valid OAuth Redirect URI<\/strong> shown in RootAuth.<\/p>\n<\/blockquote>\n <\/p>\n 2. Enable Facebook in RootAuth<\/h2>\nIn the provider list, find Facebook<\/strong> and click Enable<\/strong>.<\/p>\n In the configuration dialog, turn on Facebook login and fill in the following information:<\/p>\n \n\n\n\n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n App ID<\/td>\n Facebook App ID. Required.<\/td>\n<\/tr>\n App Secret<\/td>\n Facebook App Secret. Required.<\/td>\n<\/tr>\n Valid OAuth Redirect URI<\/td>\n Generated by RootAuth. Copy it and configure it in the Facebook app settings.<\/td>\n<\/tr>\n Permissions<\/td>\n Includes public_profile<\/code> by default. You can also select email<\/code> if needed.<\/td>\n<\/tr>\n Login mode<\/td>\n Used for login and sign-up by default<\/td>\n<\/tr>\n Account binding<\/td>\n Choose whether to automatically link accounts with the same email address<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nAfter completing the fields, click Save<\/strong>.<\/p>\n After the configuration is saved, Facebook is shown as Enabled<\/strong> and Custom credentials<\/strong>, and the action button changes to Manage<\/strong>. To update the configuration later, click Manage<\/strong>.<\/p>\n <\/p>\n <\/p>\n <\/p>\n 3. Account Binding<\/h2>\nFacebook login supports automatic account binding.<\/p>\n \nWhen Account binding<\/strong> is enabled, if the email returned by Facebook matches an existing account email in RootAuth, RootAuth automatically links the Facebook identity to that account and completes login. If no matching email is found, a new account is created.<\/li>\n When Account binding<\/strong> is disabled, Facebook login does not automatically link to an existing email account. Even if the Facebook email matches an existing account email, RootAuth creates or logs in to an independent account through the Facebook login entry.<\/li>\n<\/ul>\n\nIf accounts were previously created through different login methods, RootAuth determines which account to log in to based on the current login entry and existing account relationships after account binding is enabled.<\/p>\n<\/blockquote>\n <\/p>\n 4. How Users Log In with Facebook<\/h2>\nAfter Facebook login is enabled, the login or sign-up page displays a Facebook login button.<\/p>\n If Google, Telegram, and Facebook are enabled at the same time, the social login buttons are displayed on the login or sign-up page according to the current configuration. When a user clicks Facebook<\/strong>, they are redirected to the Facebook authorization page.<\/p>\n After the user confirms authorization, RootAuth automatically completes the following steps:<\/p>\n \nReceives the user information returned by Facebook.<\/li>\n Checks whether an existing account should be linked based on the account binding setting.<\/li>\n If an existing account can be linked, logs the user in to that account.<\/li>\n If no account can be linked, creates a new account and completes login.<\/li>\n<\/ol>\n<\/p>\n <\/p>\n 5. View a User's Facebook Authentication Method<\/h2>\nAfter a user logs in or signs up with Facebook, you can view the authentication record in the user details.<\/p>\n Go to User Management<\/strong>, open the target user's details, and check the Authentication Methods<\/strong> section.<\/p>\n The Facebook authentication method displays:<\/p>\n \n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n Authentication method<\/td>\n Facebook<\/td>\n<\/tr>\n Identifier<\/td>\n Facebook email or Facebook ID. If an email is available, the email is shown first.<\/td>\n<\/tr>\n Last used<\/td>\n The most recent time the user logged in with Facebook<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\n \nIf the application unbinds the user's Facebook account through the API, this authentication method is removed from the user details.<\/p>\n<\/blockquote>\n <\/p>\n 6. Integration Options<\/h2>\nFacebook login supports two integration options:<\/p>\n \n\n\n\n\n\nIntegration option<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n Hosted<\/td>\n Use the login and sign-up pages hosted by RootAuth. After Facebook is enabled, the Facebook login button is displayed automatically.<\/td>\n<\/tr>\n API<\/td>\n Build your own Facebook login entry in your application, then use APIs to complete login, binding, or unbinding.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nFor integration details, see the Developer Integration documentation<\/a>.<\/strong><\/p>\n <\/p>\n 7. Disable Facebook Login<\/h2>\nTo disable Facebook login, open the Facebook management dialog, turn off the switch, and save the configuration.<\/p>\n After Facebook login is disabled:<\/p>\n\nThe Facebook login button is no longer shown on the login or sign-up page.<\/li>\n The saved Facebook credentials are retained.<\/li>\n Existing users' Facebook binding records are not deleted.<\/li>\nWhen you enable it again later, you can continue using the previous configuration.<\/li>\n<\/ol>\nIf a user still sees an old cached login page and clicks Facebook login, RootAuth blocks the request and shows a login failure message. After the user refreshes the page, the latest login configuration is loaded.<\/p>","pure_content":"RootAuth supports Facebook login. After it is enabled, users can select Facebook on the login or sign-up page and complete login or registration through Facebook authorization.\nPath: Log in to the RootAuth console \u2192 open the target application \u2192 click Configuration in the top navigation bar \u2192 Application Management - Authentication Configuration \u2192 select Providers\n\u00a0\n1. Before You Start\nBefore configuring Facebook login, make sure you have completed the following:\n\nYou have a Facebook developer account.\nYou have created an app in the Facebook developer platform.\nYou have obtained the Facebook App ID and App Secret.\nYou have prepared your application domain for configuring the OAuth redirect URI.\n\n\nFacebook verifies the OAuth redirect URI. Make sure the callback URL configured in the Facebook app matches the Valid OAuth Redirect URI shown in RootAuth.\n\n\u00a0\n2. Enable Facebook in RootAuth\nIn the provider list, find Facebook and click Enable.\nIn the configuration dialog, turn on Facebook login and fill in the following information:\n\n\n\n Field\n Description\n\n\n\n\n App ID\n Facebook App ID. Required.\n\n\n App Secret\n Facebook App Secret. Required.\n\n\n Valid OAuth Redirect URI\n Generated by RootAuth. Copy it and configure it in the Facebook app settings.\n\n\n Permissions\n Includes public_profile by default. You can also select email if needed.\n\n\n Login mode\n Used for login and sign-up by default\n\n\n Account binding\n Choose whether to automatically link accounts with the same email address\n\n\n\nAfter completing the fields, click Save.\nAfter the configuration is saved, Facebook is shown as Enabled and Custom credentials, and the action button changes to Manage. To update the configuration later, click Manage.\n\n\n\u00a0\n3. Account Binding\nFacebook login supports automatic account binding.\n\nWhen Account binding is enabled, if the email returned by Facebook matches an existing account email in RootAuth, RootAuth automatically links the Facebook identity to that account and completes login. If no matching email is found, a new account is created.\nWhen Account binding is disabled, Facebook login does not automatically link to an existing email account. Even if the Facebook email matches an existing account email, RootAuth creates or logs in to an independent account through the Facebook login entry.\n\n\nIf accounts were previously created through different login methods, RootAuth determines which account to log in to based on the current login entry and existing account relationships after account binding is enabled.\n\n\u00a0\n4. How Users Log In with Facebook\nAfter Facebook login is enabled, the login or sign-up page displays a Facebook login button.\nIf Google, Telegram, and Facebook are enabled at the same time, the social login buttons are displayed on the login or sign-up page according to the current configuration. When a user clicks Facebook, they are redirected to the Facebook authorization page.\nAfter the user confirms authorization, RootAuth automatically completes the following steps:\n\nReceives the user information returned by Facebook.\nChecks whether an existing account should be linked based on the account binding setting.\nIf an existing account can be linked, logs the user in to that account.\nIf no account can be linked, creates a new account and completes login.\n\n\n\u00a0\n5. View a User's Facebook Authentication Method\nAfter a user logs in or signs up with Facebook, you can view the authentication record in the user details.\nGo to User Management, open the target user's details, and check the Authentication Methods section.\nThe Facebook authentication method displays:\n\n\n\n Field\n Description\n\n\n\n\n Authentication method\n Facebook\n\n\n Identifier\n Facebook email or Facebook ID. If an email is available, the email is shown first.\n\n\n Last used\n The most recent time the user logged in with Facebook\n\n\n\n\n\nIf the application unbinds the user's Facebook account through the API, this authentication method is removed from the user details.\n\n\u00a0\n6. Integration Options\nFacebook login supports two integration options:\n\n\n\n Integration option\n Description\n\n\n\n\n Hosted\n Use the login and sign-up pages hosted by RootAuth. After Facebook is enabled, the Facebook login button is displayed automatically.\n\n\n API\n Build your own Facebook login entry in your application, then use APIs to complete login, binding, or unbinding.\n\n\n\nFor integration details, see the Developer Integration documentation.\n\u00a0\n7. Disable Facebook Login\nTo disable Facebook login, open the Facebook management dialog, turn off the switch, and save the configuration.\nAfter Facebook login is disabled:\n\nThe Facebook login button is no longer shown on the login or sign-up page.\nThe saved Facebook credentials are retained.\nExisting users' Facebook binding records are not deleted.\nWhen you enable it again later, you can continue using the previous configuration.\n\nIf a user still sees an old cached login page and clicks Facebook login, RootAuth blocks the request and shows a login failure message. After the user refreshes the page, the latest login configuration is loaded.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1780898290","update_time":"1780976131"},"pure_content":"RootAuth supports Facebook login. After it is enabled, users can select Facebook on the login or sign-up page and complete login or registration through Facebook authorization.\nPath: Log in to the Roo"}],"content":{"icon":"","desc":"","content_id":"740501","add_time":"1773213849","update_time":"1773223613","content":"","is_traffic_less":"0","file_type":""},"hot_list":[{"id":"740502","string_id":"rcngMc1G","slug":"authentication-providers-google","name":"Google","type":"2","status":"1","order":"0","cover":"","cover_alt":"","articleOnline":{"content_id":"740502","content":" By configuring social login providers, your application users can conveniently log in or register using their own Google accounts without needing to remember additional passwords. RootAuth currently supports Google login and provides two configuration methods: Shared Credentials (for testing) and Custom Credentials (for production environments).<\/p>\n Path:<\/strong> Log in to the RootAuth console → Navigate to the target application → Click Configuration in the top navigation bar → Select Application Management – Authentication Configuration → Choose Providers<\/p>\n <\/h2>\n1. Feature Overview<\/h2>\nRootAuth's social login feature enables you to quickly integrate Google account login, enhancing the user experience. The system provides two configuration methods:<\/p>\n\n\nShared RootAuth Credentials:<\/strong> No need to apply for OAuth credentials yourself; can be used directly for testing to quickly experience the Google login process.<\/p>\n<\/li>\n\nCustom Credentials:<\/strong> You need to go to the Google Cloud Console to apply for your own OAuth Client ID and Secret. Suitable for production environments, providing full brand control and higher security.<\/p>\n<\/li>\n<\/ul>\n <\/h2>\n2. Applying for a Google OAuth Client Account<\/h2>\nTo integrate Google login into your application, you first need to create an OAuth 2.0 client in the Google Cloud Console. Follow the steps below (skip if you are already familiar).<\/p>\nStep 1: Access the Google Cloud Console<\/h3>\nOpen the Google Cloud Console<\/a> and log in with your Google account. If you don't have an account, please register first.<\/p>\n Step 2: Create or Select a Project<\/h3>\nAt the top of the console, click the project dropdown menu. Select an existing project or click \"New Project\" to create a new one, filling in the project name and other information. Ensure the current context is the project you intend to use.<\/p>\n Step 3: Navigate to \"APIs & Services\" > \"Credentials\"<\/h3>\nIn the left navigation menu, select \"APIs & Services\"<\/strong>, then click \"Credentials\"<\/strong>.<\/p>\n Step 4: Configure the OAuth Consent Screen (If First Time Use)<\/h3>\nOn the \"Credentials\" page, if prompted to \"Configure Consent Screen\", click it. If it indicates that the Google Auth Platform is not yet configured, click \"Get Started\".<\/p>\n You will enter the project configuration page. Fill in the necessary information, such as:<\/p>\n \n\nApp name<\/strong><\/p>\n<\/li>\n \nUser support email<\/strong><\/p>\n<\/li>\n \nAudience<\/strong> (select \"External\" for general applications)<\/p>\n<\/li>\n \nDeveloper contact information<\/strong><\/p>\n<\/li>\n<\/ul>\n Then click \"Create\"<\/strong>.<\/p>\n Step 5: Create an OAuth Client<\/h3>\nOn the \"Overview\" page, click \"Create OAuth Client ID\"<\/strong> and configure the relevant information.<\/p>\n The system will prompt you to select an application type. For most web applications, choose \"Web Application\"<\/strong> and fill in the following information:<\/p>\n \n\nName:<\/strong> Give your client an easily identifiable name, e.g., \"My Application - Web\".<\/p>\n<\/li>\n \nAuthorized JavaScript origins:<\/strong> Add your application's frontend domain (e.g., https:\/\/yourdomain.com<\/code>) and local development addresses (e.g., http:\/\/localhost:3000<\/code>). This helps prevent cross-site request forgery.<\/p>\n<\/li>\n \nAuthorized redirect URIs:<\/strong> This is the address Google redirects to after user authorization. You need to fill in the redirect URI obtained from the RootAuth console. Ensure this is entered accurately; otherwise, the authorization flow will fail.<\/p>\n<\/li>\n<\/ul>\n Step 6: Create and Obtain Credentials<\/h3>\nClick the \"Create\"<\/strong> button. A popup will immediately display your Client ID<\/strong> and Client Secret<\/strong>. Be sure to copy and securely store these two values<\/strong>; you will need to enter them in the RootAuth console later.<\/p>\n \n\nClient ID:<\/strong> Used to identify your application; it is the application's public identifier.<\/p>\n<\/li>\n \nClient Secret:<\/strong> Equivalent to a password. Do not disclose it. If accidentally lost, you can regenerate it in the credentials list at any time.<\/p>\n<\/li>\n<\/ul>\n Step 7: Next Steps<\/h3>\nReturn to the RootAuth console. In Authentication Management → Providers → Google Configuration<\/strong>, fill in the Client ID and Client Secret obtained above, and ensure the redirect URI matches the one you entered in the Google Cloud Console.<\/p>\n \nTip:<\/strong> If you haven't completed the configuration in RootAuth yet, you can leave it blank for now and edit the client later. However, it is recommended to have it ready in advance.<\/p>\n<\/blockquote>\n <\/h2>\n3. Configuring Google Login<\/h2>\n 3.1 Enabling Google Login<\/h3>\nFind Google<\/strong> in the providers list and click the \"Enable\"<\/strong> button on the right. A configuration popup will appear. There is a toggle switch in the upper-left corner of the popup, which is off by default. Click to turn it \"On\"<\/strong>; the credential type options below will become selectable.<\/p>\n <\/p>\n 3.2 Selecting a Credential Type<\/h3>\nThe popup provides two credential types; you need to choose one:<\/p>\n \n\nShared RootAuth Credentials<\/strong><\/p>\n \n\nDescription:<\/strong> Test Google OAuth without any setup.<\/p>\n<\/li>\n \nApplicable Scenario:<\/strong> Development testing, quick validation.<\/p>\n<\/li>\n \nAction:<\/strong> After selecting this card, simply click the \"Save\"<\/strong> button in the lower-right corner of the popup for it to take effect.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n <\/p>\n \n\nCustom Credentials<\/strong><\/p>\n \n\nDescription:<\/strong> Configure your own Google OAuth for production environments.<\/p>\n<\/li>\n \nApplicable Scenario:<\/strong> Official launch; requires you to apply for Google OAuth credentials yourself.<\/p>\n<\/li>\n \nAction:<\/strong> After selecting this card, a detailed configuration form will expand below. Complete the form before saving.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n <\/p>\n Custom Credentials Form Field Descriptions<\/strong><\/p>\n \n\n\n\n\n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n Required<\/th>\n<\/tr>\n<\/thead>\n Google Client ID<\/strong><\/td>\n The Client ID you generated in the Google Cloud Console<\/td>\n Yes<\/td>\n<\/tr>\n Google Client Secret<\/strong><\/td>\n The corresponding Client Secret; input is masked<\/td>\n Yes<\/td>\n<\/tr>\n Authorized Redirect URI<\/strong><\/td>\n Automatically generated by the system. You need to copy this URI and fill it in as a callback address in the Google Cloud Console<\/td>\n Read-only<\/td>\n<\/tr>\n Authorization Scope<\/strong><\/td>\n Fixed as email, profile, openid<\/code>; no modification needed<\/td>\n Read-only<\/td>\n<\/tr>\n Login Mode<\/strong><\/td>\n Fixed as \"Available for login\/registration\", meaning users can log in or register via Google<\/td>\n Checked by default, cannot be modified<\/td>\n<\/tr>\n Account Linking<\/strong><\/td>\n If the email used for Google login matches an existing account email in the system, it is automatically linked; otherwise, a new account is created<\/td>\n Checked by default, cannot be modified<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n\nNote:<\/strong> When filling in the Client ID and Secret, the system does not validate their format or validity. Actual verification occurs during the OAuth flow when a user logs in with Google for the first time.<\/p>\n<\/blockquote>\n 3.3 Saving the Configuration<\/h3>\nAfter making your selection or filling in the form, click the \"Save\"<\/strong> button in the lower-right corner of the popup. Upon successful saving, the popup closes, and the status for Google in the providers list changes to \"Enabled\"<\/strong>. If you selected Custom Credentials, it will be tagged as \"Custom Credentials\"<\/strong>, and the button on the right will change to \"Manage\"<\/strong>.<\/p>\n <\/h2>\n4. Managing an Enabled Configuration<\/h2>\nClick the \"Manage\"<\/strong> button next to Google to reopen the configuration popup.<\/p>\n The popup will fully load the configuration state you last saved (toggle state, selected credential type, and any custom information entered).<\/p>\n You can modify the configuration within the popup (e.g., switch credential types, update custom credential fields). After making changes, click \"Save\"<\/strong> for them to take effect.<\/p>\n To disable Google login, turn off the toggle switch at the top of the popup and click \"Save\"<\/strong>. Once disabled, the Google button will no longer be displayed on the end-user login page.<\/p>\n \nNote:<\/strong> After disabling Google login, any previously entered custom credential information is retained, so you won't need to re-enter it if you enable it again later.<\/p>\n<\/blockquote>\n <\/h2>\n5. End-User Experience<\/h2>\nOnce the configuration takes effect, a Google login button<\/strong> will automatically appear on your application's login and registration pages. You can preview the effect via Application – Application Management – Try Registration\/Login<\/strong> in the upper-right corner. When users click this button, they will be redirected to the Google authorization page; after consenting, they can quickly log in or register.<\/p>\n \n\nIf the email used for Google login already exists in your application's user pool, the system will automatically link the accounts.<\/p>\n<\/li>\n \nOtherwise, a new user account will be created automatically.<\/p>\n<\/li>\n<\/ul>\n <\/p>\n \nNote on Caching:<\/strong> Due to possible browser or CDN caching, it may take up to 2 minutes for configuration changes to be fully effective for all end-users. If a user clicks the old button and encounters a prompt, refreshing the page should load the latest configuration.<\/p>\n<\/blockquote>\n <\/h2>\n6. Viewing a User's Linked Google Account<\/h2>\nIn the User Management → User Details<\/strong> page of your application, within the \"Authentication Methods\"<\/strong> section, you can view information about the user's linked Google account:<\/p>\n \n\nGoogle icon and name<\/p>\n<\/li>\n \nLinked Google email address<\/p>\n<\/li>\n \nTime of the last login using Google<\/p>\n<\/li>\n<\/ul>\n Currently, this information is for display purposes only; manual unlinking is not supported.<\/p>\n <\/p>","pure_content":"By configuring social login providers, your application users can conveniently log in or register using their own Google accounts without needing to remember additional passwords. RootAuth currently supports Google login and provides two configuration methods: Shared Credentials (for testing) and Custom Credentials (for production environments).\nPath:\u00a0Log in to the RootAuth console \u2192 Navigate to the target application \u2192 Click\u00a0Configuration\u00a0in the top navigation bar \u2192 Select\u00a0Application Management \u2013 Authentication Configuration\u00a0\u2192 Choose\u00a0Providers\n\u00a0\n1. Feature Overview\nRootAuth's social login feature enables you to quickly integrate Google account login, enhancing the user experience. The system provides two configuration methods:\n\n\nShared RootAuth Credentials:\u00a0No need to apply for OAuth credentials yourself; can be used directly for testing to quickly experience the Google login process.\n\n\nCustom Credentials:\u00a0You need to go to the Google Cloud Console to apply for your own OAuth Client ID and Secret. Suitable for production environments, providing full brand control and higher security.\n\n\n\u00a0\n2. Applying for a Google OAuth Client Account\nTo integrate Google login into your application, you first need to create an OAuth 2.0 client in the Google Cloud Console. Follow the steps below (skip if you are already familiar).\nStep 1: Access the Google Cloud Console\nOpen the\u00a0Google Cloud Console\u00a0and log in with your Google account. If you don't have an account, please register first.\nStep 2: Create or Select a Project\nAt the top of the console, click the project dropdown menu. Select an existing project or click \"New Project\" to create a new one, filling in the project name and other information. Ensure the current context is the project you intend to use.\nStep 3: Navigate to \"APIs & Services\" > \"Credentials\"\nIn the left navigation menu, select\u00a0\"APIs & Services\", then click\u00a0\"Credentials\".\nStep 4: Configure the OAuth Consent Screen (If First Time Use)\nOn the \"Credentials\" page, if prompted to \"Configure Consent Screen\", click it. If it indicates that the Google Auth Platform is not yet configured, click \"Get Started\".\nYou will enter the project configuration page. Fill in the necessary information, such as:\n\n\nApp name\n\n\nUser support email\n\n\nAudience\u00a0(select \"External\" for general applications)\n\n\nDeveloper contact information\n\n\nThen click\u00a0\"Create\".\nStep 5: Create an OAuth Client\nOn the \"Overview\" page, click\u00a0\"Create OAuth Client ID\"\u00a0and configure the relevant information.\nThe system will prompt you to select an application type. For most web applications, choose\u00a0\"Web Application\"\u00a0and fill in the following information:\n\n\nName:\u00a0Give your client an easily identifiable name, e.g., \"My Application - Web\".\n\n\nAuthorized JavaScript origins:\u00a0Add your application's frontend domain (e.g.,\u00a0https:\/\/yourdomain.com) and local development addresses (e.g.,\u00a0http:\/\/localhost:3000). This helps prevent cross-site request forgery.\n\n\nAuthorized redirect URIs:\u00a0This is the address Google redirects to after user authorization. You need to fill in the redirect URI obtained from the RootAuth console. Ensure this is entered accurately; otherwise, the authorization flow will fail.\n\n\nStep 6: Create and Obtain Credentials\nClick the\u00a0\"Create\"\u00a0button. A popup will immediately display your\u00a0Client ID\u00a0and\u00a0Client Secret.\u00a0Be sure to copy and securely store these two values; you will need to enter them in the RootAuth console later.\n\n\nClient ID:\u00a0Used to identify your application; it is the application's public identifier.\n\n\nClient Secret:\u00a0Equivalent to a password. Do not disclose it. If accidentally lost, you can regenerate it in the credentials list at any time.\n\n\nStep 7: Next Steps\nReturn to the RootAuth console. In\u00a0Authentication Management \u2192 Providers \u2192 Google Configuration, fill in the Client ID and Client Secret obtained above, and ensure the redirect URI matches the one you entered in the Google Cloud Console.\n\nTip:\u00a0If you haven't completed the configuration in RootAuth yet, you can leave it blank for now and edit the client later. However, it is recommended to have it ready in advance.\n\n\u00a0\n3. Configuring Google Login\n3.1 Enabling Google Login\nFind\u00a0Google\u00a0in the providers list and click the\u00a0\"Enable\"\u00a0button on the right. A configuration popup will appear. There is a toggle switch in the upper-left corner of the popup, which is off by default. Click to turn it\u00a0\"On\"; the credential type options below will become selectable.\n\n3.2 Selecting a Credential Type\nThe popup provides two credential types; you need to choose one:\n\n\nShared RootAuth Credentials\n\n\nDescription:\u00a0Test Google OAuth without any setup.\n\n\nApplicable Scenario:\u00a0Development testing, quick validation.\n\n\nAction:\u00a0After selecting this card, simply click the\u00a0\"Save\"\u00a0button in the lower-right corner of the popup for it to take effect.\n\n\n\n\n\n\n\nCustom Credentials\n\n\nDescription:\u00a0Configure your own Google OAuth for production environments.\n\n\nApplicable Scenario:\u00a0Official launch; requires you to apply for Google OAuth credentials yourself.\n\n\nAction:\u00a0After selecting this card, a detailed configuration form will expand below. Complete the form before saving.\n\n\n\n\n\nCustom Credentials Form Field Descriptions\n\n\n\n\n Field\n Description\n Required\n\n\n\n\n Google Client ID\n The Client ID you generated in the Google Cloud Console\n Yes\n\n\n Google Client Secret\n The corresponding Client Secret; input is masked\n Yes\n\n\n Authorized Redirect URI\n Automatically generated by the system. You need to copy this URI and fill it in as a callback address in the Google Cloud Console\n Read-only\n\n\n Authorization Scope\n Fixed as\u00a0email, profile, openid; no modification needed\n Read-only\n\n\n Login Mode\n Fixed as \"Available for login\/registration\", meaning users can log in or register via Google\n Checked by default, cannot be modified\n\n\n Account Linking\n If the email used for Google login matches an existing account email in the system, it is automatically linked; otherwise, a new account is created\n Checked by default, cannot be modified\n\n\n\n\n\nNote:\u00a0When filling in the Client ID and Secret, the system does not validate their format or validity. Actual verification occurs during the OAuth flow when a user logs in with Google for the first time.\n\n3.3 Saving the Configuration\nAfter making your selection or filling in the form, click the\u00a0\"Save\"\u00a0button in the lower-right corner of the popup. Upon successful saving, the popup closes, and the status for Google in the providers list changes to\u00a0\"Enabled\". If you selected Custom Credentials, it will be tagged as\u00a0\"Custom Credentials\", and the button on the right will change to\u00a0\"Manage\".\n\u00a0\n4. Managing an Enabled Configuration\nClick the\u00a0\"Manage\"\u00a0button next to Google to reopen the configuration popup.\nThe popup will fully load the configuration state you last saved (toggle state, selected credential type, and any custom information entered).\nYou can modify the configuration within the popup (e.g., switch credential types, update custom credential fields). After making changes, click\u00a0\"Save\"\u00a0for them to take effect.\nTo disable Google login, turn off the toggle switch at the top of the popup and click\u00a0\"Save\". Once disabled, the Google button will no longer be displayed on the end-user login page.\n\nNote:\u00a0After disabling Google login, any previously entered custom credential information is retained, so you won't need to re-enter it if you enable it again later.\n\n\u00a0\n5. End-User Experience\nOnce the configuration takes effect, a\u00a0Google login button\u00a0will automatically appear on your application's login and registration pages. You can preview the effect via\u00a0Application \u2013 Application Management \u2013 Try Registration\/Login\u00a0in the upper-right corner. When users click this button, they will be redirected to the Google authorization page; after consenting, they can quickly log in or register.\n\n\nIf the email used for Google login already exists in your application's user pool, the system will automatically link the accounts.\n\n\nOtherwise, a new user account will be created automatically.\n\n\n\n\nNote on Caching:\u00a0Due to possible browser or CDN caching, it may take up to 2 minutes for configuration changes to be fully effective for all end-users. If a user clicks the old button and encounters a prompt, refreshing the page should load the latest configuration.\n\n\u00a0\n6. Viewing a User's Linked Google Account\nIn the\u00a0User Management \u2192 User Details\u00a0page of your application, within the\u00a0\"Authentication Methods\"\u00a0section, you can view information about the user's linked Google account:\n\n\nGoogle icon and name\n\n\nLinked Google email address\n\n\nTime of the last login using Google\n\n\nCurrently, this information is for display purposes only; manual unlinking is not supported.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1773213853","update_time":"1779161827"},"pure_content":"By configuring social login providers, your application users can conveniently log in or register using their own Google accounts without needing to remember additional passwords. RootAuth currently s"}],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}