{"data":{"id":"740535","string_id":"Jm2onXZi","status":"1","parent_id":"740398","slug":"security-settings","order":"6","name":"Security Settings","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"0","add_time":"1773215113","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":"740536","string_id":"MLowRk2Q","status":"1","parent_id":"740535","slug":"general-security","order":"0","name":"General Security","type":"1","cover":"","cover_alt":"","desc":"

General Security is used to configure global security protection policies for the current application. All configurations apply only to the current application and directly affect end-user authentication processes such as registration, login, and password reset. These settings are also reflected in real time on the Try Registration\/Login<\/strong> preview page.<\/p>","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1773215123","update_time":"1773223781","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"740536\", \"740535\", \"740398\"]","pure_content":"General Security is used to configure global security protection policies for the current application. All configurations apply only to the current application and directly affect end-user authenticat"},{"id":"740540","string_id":"7z7gY4wk","status":"1","parent_id":"740535","slug":"risk-policies","order":"0","name":"Risk Policies","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1773215373","update_time":"1773223798","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"740540\", \"740535\", \"740398\"]","pure_content":""},{"id":"792071","string_id":"xtTGv7dS","status":"1","parent_id":"740535","slug":"mfa","order":"0","name":"Multi-factor Authentication","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1778846096","update_time":"1778846107","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"792071\", \"740535\", \"740398\"]","pure_content":""}],"content":{"icon":"","desc":"

This section covers the security protection configurations for applications, including General Security<\/strong> (such as Registration Security) and Risk Policies<\/strong> (such as IP Blacklist), helping you build a multi-layered defense system to protect against various security risks.<\/p>","is_traffic_less":"0","file_type":""},"hot_list":[{"id":"740537","string_id":"IE54dsbU","slug":"registration-security","name":"Registration Security","type":"2","status":"1","order":"0","cover":"","cover_alt":"","articleOnline":{"content_id":"740537","content":"

\n
Registration security is used to configure security protection policies for the application registration process, including disposable email blocking and human verification (CAPTCHA), effectively preventing fake account registrations and automated attacks.<\/p>\n
Path:<\/strong> Log in to the RootAuth console → Navigate to the target application → Click Configuration in the top navigation bar → Select Security Settings – General Security → Registration Security<\/p>\n
<\/h2>\n
1. Disposable Email Policy<\/h2>\n
\n\n\n\n\n\n
Configuration Item<\/th>\n Description<\/th>\n Default Status<\/th>\n<\/tr>\n<\/thead>\n
Block registrations using disposable email addresses<\/strong><\/td>\n When enabled, the system will identify and block the use of temporary email addresses (such as 10-minute email, disposable email) for registration, effectively preventing fake accounts.<\/td>\n Checked by default<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
How It Works:<\/strong><\/p>\n
\n
\n
When a user submits registration using a domain that is recognized by the industry as a \"disposable email\" domain, the system will directly block the registration attempt and display a prompt.<\/p>\n<\/li>\n
\n
This blocking occurs after the user has correctly filled in the registration information and clicks the \"Register\"<\/strong> button.<\/p>\n<\/li>\n
\n
If this option is disabled, any email address can be used for registration.<\/p>\n<\/li>\n<\/ul>\n
Scope of Impact:<\/strong> Only affects the registration process of the current application; does not interfere with other applications.<\/p>\n
<\/h2>\n
2. Human Verification (CAPTCHA) Policy<\/h2>\n
\n\n\n\n\n\n\n\n
Configuration Item<\/th>\n Description<\/th>\n Default Status<\/th>\n<\/tr>\n<\/thead>\n
Users must always pass human verification before sending a verification code<\/strong><\/td>\n When enabled, users must first pass a graphical CAPTCHA (e.g., slider, click-based) when clicking \"Get Verification Code\"<\/strong> during registration, login (via verification code), or password reset. This prevents automated attacks.<\/td>\n Checked by default<\/td>\n<\/tr>\n
Slider Verification<\/strong><\/td>\n Users complete a slider puzzle manually with explicit interaction, suitable for most scenarios.<\/td>\n Checked by default<\/td>\n<\/tr>\n
Invisible Verification<\/strong><\/td>\n Behavior is analyzed in the background, low-risk users pass without friction; slider verification appears only when anomalies are detected.<\/td>\n Switchable mode<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Covered Scenarios:<\/strong><\/p>\n
\n
\n
Registration process: obtaining an email activation code<\/p>\n<\/li>\n
\n
Verification code login: obtaining a login verification code<\/p>\n<\/li>\n
\n
Password reset: obtaining a password reset verification code<\/p>\n<\/li>\n<\/ul>\n
Interaction Description:<\/strong><\/p>\n
\n
\n
When enabled, clicking the corresponding button (\"Get Activation Code\"<\/strong>, \"Get Verification Code\"<\/strong>, \"Send Verification Code\"<\/strong>) will immediately trigger the CAPTCHA popup. The email is sent only after the CAPTCHA is successfully completed.<\/p>\n<\/li>\n
\n
When disabled, clicking the button will directly send the verification code without a CAPTCHA challenge.<\/p>\n<\/li>\n<\/ul>\n
<\/p>\n
\n
Note:<\/strong> The password login scenario does not involve sending a verification code and is therefore not affected by this configuration.<\/p>\n<\/blockquote>\n
<\/h2>\n
3. Configuration Effect and Experience Verification<\/h2>\n
\n
\n
Effectiveness Time:<\/strong> After modifying any configuration items, click \"Save\"<\/strong>. The changes will take effect within 2 minutes<\/strong> without needing to restart the application.<\/p>\n<\/li>\n
\n
Experience Verification:<\/strong> You can quickly preview the effect of the security policies by clicking the \"Try Registration\/Login\"<\/strong> button in the upper-right corner of the current application page:<\/p>\n
\n
\n
Attempt to register using a temporary email address to verify the blocking prompt.<\/p>\n<\/li>\n
\n
Attempt to obtain a verification code to confirm whether the CAPTCHA popup appears.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div>","pure_content":"Registration security is used to configure security protection policies for the application registration process, including disposable email blocking and human verification (CAPTCHA), effectively preventing fake account registrations and automated attacks.\nPath:\u00a0Log in to the RootAuth console \u2192 Navigate to the target application \u2192 Click\u00a0Configuration\u00a0in the top navigation bar \u2192 Select\u00a0Security Settings \u2013 General Security\u00a0\u2192\u00a0Registration Security\n\u00a0\n1. Disposable Email Policy\n\n\n\n\n Configuration Item\n Description\n Default Status\n\n\n\n\n Block registrations using disposable email addresses\n When enabled, the system will identify and block the use of temporary email addresses (such as 10-minute email, disposable email) for registration, effectively preventing fake accounts.\n Checked by default\n\n\n\n\nHow It Works:\n\n\nWhen a user submits registration using a domain that is recognized by the industry as a \"disposable email\" domain, the system will directly block the registration attempt and display a prompt.\n\n\nThis blocking occurs after the user has correctly filled in the registration information and clicks the\u00a0\"Register\"\u00a0button.\n\n\nIf this option is disabled, any email address can be used for registration.\n\n\nScope of Impact: Only affects the registration process of the current application; does not interfere with other applications.\n\n2. Human Verification (CAPTCHA) Policy\n\n\n\n\n Configuration Item\n Description\n Default Status\n\n\n\n\n Users must always pass human verification before sending a verification code\n When enabled, users must first pass a graphical CAPTCHA (e.g., slider, click-based) when clicking\u00a0\"Get Verification Code\"\u00a0during registration, login (via verification code), or password reset. This prevents automated attacks.\n Checked by default\n\n\n Slider Verification\n Users complete a slider puzzle manually with explicit interaction, suitable for most scenarios.\n Checked by default\n\n\n Invisible Verification\n Behavior is analyzed in the background, low-risk users pass without friction; slider verification appears only when anomalies are detected.\n Switchable mode\n\n\n\n\nCovered Scenarios:\n\n\nRegistration process: obtaining an email activation code\n\n\nVerification code login: obtaining a login verification code\n\n\nPassword reset: obtaining a password reset verification code\n\n\nInteraction Description:\n\n\nWhen enabled, clicking the corresponding button (\"Get Activation Code\",\u00a0\"Get Verification Code\",\u00a0\"Send Verification Code\") will immediately trigger the CAPTCHA popup. The email is sent only after the CAPTCHA is successfully completed.\n\n\nWhen disabled, clicking the button will directly send the verification code without a CAPTCHA challenge.\n\n\n\n\nNote: The password login scenario does not involve sending a verification code and is therefore not affected by this configuration.\n\n\u00a0\n3. Configuration Effect and Experience Verification\n\n\nEffectiveness Time:\u00a0After modifying any configuration items, click\u00a0\"Save\". The changes will take effect within\u00a02 minutes\u00a0without needing to restart the application.\n\n\nExperience Verification:\u00a0You can quickly preview the effect of the security policies by clicking the\u00a0\"Try Registration\/Login\"\u00a0button in the upper-right corner of the current application page:\n\n\nAttempt to register using a temporary email address to verify the blocking prompt.\n\n\nAttempt to obtain a verification code to confirm whether the CAPTCHA popup appears.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1773215125","update_time":"1779162111"},"pure_content":"Registration security is used to configure security protection policies for the application registration process, including disposable email blocking and human verification (CAPTCHA), effectively pre"},{"id":"740541","string_id":"KuB1cPRZ","slug":"ip-blacklist","name":"IP Blacklist","type":"2","status":"1","order":"0","cover":"","cover_alt":"","articleOnline":{"content_id":"740541","content":"
\n
\n
The IP blacklist is used to restrict access from specific IP addresses. Once an IP address is added to the blacklist, any registration or login requests originating from that IP will be automatically rejected by the system. This feature effectively mitigates malicious activities such as brute-force attacks and bulk registrations, enhancing application security.<\/p>\n
Path:<\/strong> Log in to the RootAuth console → Navigate to the target application → Click C<\/strong>onfiguration in the top navigation bar → Select Security Settings – Risk Policies → IP Blacklist<\/p>\n
<\/p>\n
1. Feature Overview<\/h2>\n
\n
\n
After adding specific IP addresses to the blacklist, registration or login requests from these IPs will be automatically rejected by the system.<\/p>\n<\/li>\n
\n
Supports batch addition of multiple IP addresses, with each IP managed independently, allowing for flexible control.<\/p>\n<\/li>\n
\n
All configurations apply only to the current application and are isolated from other applications, ensuring no interference.<\/p>\n<\/li>\n<\/ul>\n
<\/h2>\n
2. Operation Guide<\/h2>\n
2.1 Viewing the Blacklist<\/h3>\n
The blacklist page displays all added IP records in a table format, with 10 entries per page by default.<\/p>\n
\n\n\n\n\n\n\n\n\n
Field<\/th>\n Description<\/th>\n Example<\/th>\n<\/tr>\n<\/thead>\n
IP<\/strong><\/td>\n The restricted IP address<\/td>\n 183.6.116.162<\/td>\n<\/tr>\n
Restriction Type<\/strong><\/td>\n Fixed as \"Block Registration\/Login\"<\/td>\n Block Registration\/Login<\/td>\n<\/tr>\n
Added Time<\/strong><\/td>\n The time the record was added, in the format YYYY-MM-DD HH:mm:ss<\/code>, automatically converted to your browser's time zone<\/td>\n 2026-02-26 17:30:27<\/td>\n<\/tr>\n
Actions<\/strong><\/td>\n Click \"Delete\" to remove the IP from the blacklist<\/td>\n [Delete]<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
List Operations:<\/strong><\/p>\n
\n
\n
Search:<\/strong> The search box in the upper-left corner of the list supports fuzzy searching by IP address, allowing you to quickly locate target records.<\/p>\n<\/li>\n
\n
Refresh:<\/strong> The list automatically refreshes after adding or deleting IPs.<\/p>\n<\/li>\n<\/ul>\n
<\/p>\n
<\/h3>\n
2.2 Adding an IP to the Blacklist<\/h3>\n
Click the \"+ Add IP\"<\/strong> button in the upper-right corner of the list to open the addition window.<\/p>\n
Field Descriptions:<\/strong><\/p>\n
\n\n\n\n\n\n\n
Field<\/th>\n Required<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n
IP<\/strong><\/td>\n Yes<\/td>\n Supports a single IP (e.g., 123.45.67.89<\/code>) or multiple IPs. For multiple IPs, separate them with commas (e.g., 123.45.67.89, 203.0.113.5<\/code>). A maximum of 100 IPs can be added at once.<\/td>\n<\/tr>\n
Restriction Type<\/strong><\/td>\n Yes<\/td>\n Fixed as \"Block Registration\/Login\" and cannot be changed.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Important Notes During Addition:<\/strong><\/p>\n
\n
\n
Format Validation:<\/strong> The system will check the format of each IP in real time as you type. If the format is incorrect, you will be immediately prompted to correct it.<\/p>\n<\/li>\n
\n
Duplicate Handling:<\/strong> Upon submission, the system automatically filters out IPs that already exist in the blacklist and only adds new ones. No additional action is required from you.<\/p>\n<\/li>\n
\n
Addition Result:<\/strong> Regardless of how many IPs you add at once, each IP will appear as a separate record in the list for convenient individual management.<\/p>\n<\/li>\n<\/ul>\n
Steps:<\/strong><\/p>\n
\n
\n
Enter the IP address(es) you want to restrict in the input field.<\/p>\n<\/li>\n
\n
Click \"Confirm\"<\/strong> to save.<\/p>\n<\/li>\n
\n
The window closes, and the list automatically refreshes. The newly added IP(s) take effect immediately.<\/p>\n<\/li>\n<\/ol>\n
<\/p>\n
\n
Tip:<\/strong> If you want to temporarily test whether a specific IP is blocked, you can add it and then delete it—it's a simple process.<\/p>\n<\/blockquote>\n
<\/h3>\n
2.3 Removing an IP from the Blacklist<\/h3>\n
When an IP no longer needs to be restricted, you can remove it from the blacklist:<\/p>\n
\n
\n
Locate the IP you want to remove in the list.<\/p>\n<\/li>\n
\n
Click the \"Delete\"<\/strong> button in the corresponding row.<\/p>\n<\/li>\n
\n
In the confirmation dialog that appears, click \"Confirm\"<\/strong> to complete the removal.<\/p>\n<\/li>\n<\/ol>\n
<\/h2>\n
<\/h2>\n
3. Usage Recommendations and Verification<\/h2>\n
3.1 When to Use the IP Blacklist?<\/h3>\n
\n
\n
When you notice a specific IP repeatedly failing login attempts (suspected brute-force attack).<\/p>\n<\/li>\n
\n
When you detect bulk registration activity originating from certain IP ranges.<\/p>\n<\/li>\n
\n
When you need to temporarily block access from a specific IP.<\/p>\n<\/li>\n<\/ul>\n
3.2 How to Verify That the Configuration Is Effective?<\/h3>\n
You can quickly test it as follows:<\/p>\n
\n
\n
Add your current device's public IP address to the blacklist.<\/p>\n<\/li>\n
\n
Attempt to access the application's login or registration page.<\/p>\n<\/li>\n
\n
You will find that the login\/registration request is rejected, confirming that the blacklist is active.<\/p>\n<\/li>\n<\/ol>\n
\n
Note:<\/strong> Remember to remove your IP from the blacklist after testing to avoid affecting normal usage.<\/p>\n<\/blockquote>\n<\/div>\n<\/div>\n
<\/div>\n
\n
\n
\n
<\/div>\n
<\/div>\n
<\/div>\n<\/div>\n
\n
<\/div>\n
<\/div>\n
<\/div>\n<\/div>\n
\n
<\/div>\n
<\/div>\n
<\/div>\n<\/div>\n
\n
<\/div>\n
<\/div>\n
<\/div>\n<\/div>\n
\n
<\/div>\n
<\/div>\n<\/div>\n<\/div>\n<\/div>","pure_content":"The IP blacklist is used to restrict access from specific IP addresses. Once an IP address is added to the blacklist, any registration or login requests originating from that IP will be automatically rejected by the system. This feature effectively mitigates malicious activities such as brute-force attacks and bulk registrations, enhancing application security.\nPath:\u00a0Log in to the RootAuth console \u2192 Navigate to the target application \u2192 Click\u00a0Configuration in the top navigation bar \u2192 Select Security Settings \u2013 Risk Policies \u2192 IP Blacklist\n\u00a0\n1. Feature Overview\n\n\nAfter adding specific IP addresses to the blacklist, registration or login requests from these IPs will be automatically rejected by the system.\n\n\nSupports batch addition of multiple IP addresses, with each IP managed independently, allowing for flexible control.\n\n\nAll configurations apply only to the current application and are isolated from other applications, ensuring no interference.\n\n\n\u00a0\n2. Operation Guide\n2.1 Viewing the Blacklist\nThe blacklist page displays all added IP records in a table format, with 10 entries per page by default.\n\n\n\n\n Field\n Description\n Example\n\n\n\n\n IP\n The restricted IP address\n 183.6.116.162\n\n\n Restriction Type\n Fixed as \"Block Registration\/Login\"\n Block Registration\/Login\n\n\n Added Time\n The time the record was added, in the format\u00a0YYYY-MM-DD HH:mm:ss, automatically converted to your browser's time zone\n 2026-02-26 17:30:27\n\n\n Actions\n Click \"Delete\" to remove the IP from the blacklist\n [Delete]\n\n\n\n\nList Operations:\n\n\nSearch:\u00a0The search box in the upper-left corner of the list supports fuzzy searching by IP address, allowing you to quickly locate target records.\n\n\nRefresh: The list automatically refreshes after adding or deleting IPs.\n\n\n\n\u00a0\n2.2 Adding an IP to the Blacklist\nClick the\u00a0\"+ Add IP\"\u00a0button in the upper-right corner of the list to open the addition window.\nField Descriptions:\n\n\n\n\n Field\n Required\n Description\n\n\n\n\n IP\n Yes\n Supports a single IP (e.g.,\u00a0123.45.67.89) or multiple IPs. For multiple IPs, separate them with commas (e.g.,\u00a0123.45.67.89, 203.0.113.5). A maximum of 100 IPs can be added at once.\n\n\n Restriction Type\n Yes\n Fixed as \"Block Registration\/Login\" and cannot be changed.\n\n\n\n\nImportant Notes During Addition:\n\n\nFormat Validation:\u00a0The system will check the format of each IP in real time as you type. If the format is incorrect, you will be immediately prompted to correct it.\n\n\nDuplicate Handling:\u00a0Upon submission, the system automatically filters out IPs that already exist in the blacklist and only adds new ones. No additional action is required from you.\n\n\nAddition Result:\u00a0Regardless of how many IPs you add at once, each IP will appear as a separate record in the list for convenient individual management.\n\n\nSteps:\n\n\nEnter the IP address(es) you want to restrict in the input field.\n\n\nClick\u00a0\"Confirm\"\u00a0to save.\n\n\nThe window closes, and the list automatically refreshes. The newly added IP(s) take effect immediately.\n\n\n\n\nTip: If you want to temporarily test whether a specific IP is blocked, you can add it and then delete it\u2014it's a simple process.\n\n\u00a0\n2.3 Removing an IP from the Blacklist\nWhen an IP no longer needs to be restricted, you can remove it from the blacklist:\n\n\nLocate the IP you want to remove in the list.\n\n\nClick the\u00a0\"Delete\"\u00a0button in the corresponding row.\n\n\nIn the confirmation dialog that appears, click\u00a0\"Confirm\" to complete the removal.\n\n\n\n\u00a0\n3. Usage Recommendations and Verification\n3.1 When to Use the IP Blacklist?\n\n\nWhen you notice a specific IP repeatedly failing login attempts (suspected brute-force attack).\n\n\nWhen you detect bulk registration activity originating from certain IP ranges.\n\n\nWhen you need to temporarily block access from a specific IP.\n\n\n3.2 How to Verify That the Configuration Is Effective?\nYou can quickly test it as follows:\n\n\nAdd your current device's public IP address to the blacklist.\n\n\nAttempt to access the application's login or registration page.\n\n\nYou will find that the login\/registration request is rejected, confirming that the blacklist is active.\n\n\n\nNote:\u00a0Remember to remove your IP from the blacklist after testing to avoid affecting normal usage.\n\n\n\n\u00a0\n\n\n\n\u00a0\n\u00a0\n\u00a0\n\n\n\u00a0\n\u00a0\n\u00a0\n\n\n\u00a0\n\u00a0\n\u00a0\n\n\n\u00a0\n\u00a0\n\u00a0\n\n\n\u00a0\n\u00a0","is_draft":"0","editor_type":"3","file_path":"","add_time":"1773215382","update_time":"1779162229"},"pure_content":"The IP blacklist is used to restrict access from specific IP addresses. Once an IP address is added to the blacklist, any registration or login requests originating from that IP will be automaticall"},{"id":"759712","string_id":"aOAFROqR","slug":"ip-whitelist","name":"IP Whitelist","type":"2","status":"1","order":"0","cover":"","cover_alt":"","articleOnline":{"content_id":"759712","content":"
he IP Whitelist feature allows you to designate a set of trusted IP addresses. Only registration or login requests originating from these IPs will be permitted. Once the Whitelist is enabled, any IP not on the list will be denied access, effectively enhancing your application's security.<\/p>\n
Path<\/strong>: Console → Enter a specific application → Left navigation\u300cConfiguration\u300d→ \u300cSecurity Settings\u300d→ \u300cRisk Policies\u300d→ Select “IP Whitelist”<\/strong> tab<\/p>\n
<\/h2>\n
1. Feature Overview<\/h2>\n
\n
\n
IP addresses in the Whitelist are permitted to perform registration and login operations (the restriction type is fixed as “Allow registration\/login”).<\/p>\n<\/li>\n
\n
When processing a request, the system checks the blacklist first, then the Whitelist.<\/p>\n
\n
\n
If the IP is on the blacklist, it is directly rejected.<\/p>\n<\/li>\n
\n
If the IP is not on the blacklist but the Whitelist is configured (at least one entry), then only IPs on the Whitelist are permitted; all other IPs are rejected.<\/p>\n<\/li>\n
\n
If the Whitelist is empty (no IP configured), then no Whitelist restriction applies – all IPs are allowed (though they are still subject to blacklist checks).<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
\n
All configurations are managed per application and are independent of each other.<\/p>\n<\/li>\n<\/ul>\n
<\/h2>\n
2. Whitelist List Page<\/h2>\n
The list page displays all added IP Whitelist entries in a table, supporting search and pagination.<\/p>\n
\n\n\n\n\n\n\n\n\n
Field<\/th>\n Description<\/th>\n Example<\/th>\n<\/tr>\n<\/thead>\n
IP<\/strong><\/td>\n The permitted IP address<\/td>\n 183.6.116.162<\/code><\/td>\n<\/tr>\n
Restriction Type<\/strong><\/td>\n Fixed as “Allow registration\/login”<\/td>\n Allow registration\/login<\/td>\n<\/tr>\n
Added Time<\/strong><\/td>\n Time the record was added, format YYYY-MM-DD HH:mm:ss<\/code>, automatically converted to your browser's timezone<\/td>\n 2026-04-02 11:05:51<\/code><\/td>\n<\/tr>\n
Actions<\/strong><\/td>\n A “Delete” button to remove the IP<\/td>\n [Delete]<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\nList operations<\/strong>:<\/p>\n \n\nSearch<\/strong>: A search box at the top left of the list supports fuzzy search by IP address.<\/p>\n<\/li>\n \nAdd IP<\/strong>: The “+ Add IP”<\/strong> button at the top right of the list opens an add modal.<\/p>\n<\/li>\n<\/ul>\n <\/h2>\n3. Adding an IP to the Whitelist<\/h2>\nClick the “+ Add IP”<\/strong> button to open a modal for entering the IP addresses to be allowed.<\/p>\n 3.1Form fields<\/h3>\n\n\n\n\n\n\n\nField<\/th>\n Description<\/th>\n Required<\/th>\n Rules<\/th>\n<\/tr>\n<\/thead>\n IP<\/strong><\/td>\n IP address(es) to add to the Whitelist<\/td>\n Yes<\/td>\n Supports a single IP (e.g., 123.45.67.89<\/code>) or multiple IPs separated by English commas<\/strong> (e.g., 123.45.67.89, 203.0.113.5<\/code>). Maximum of 100<\/strong> IPs per batch.<\/td>\n<\/tr>\n Restriction Type<\/strong><\/td>\n Fixed as “Allow registration\/login”, not changeable<\/td>\n Yes<\/td>\n —<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n3.2Validation rules<\/h3>\n\n\nFrontend real\u2011time validation<\/strong>: Checks each IP format and correct comma separation. If invalid, an immediate prompt is shown (e.g., “Please enter a valid IP address”).<\/p>\n<\/li>\n \nBackend duplicate check<\/strong>: After submission, the system processes each IP individually. Any IP already on the Whitelist is automatically skipped without duplication<\/strong> and no user notification<\/strong> is shown. Only new IPs are successfully added.<\/p>\n<\/li>\n<\/ul>\n 3.3Saving and feedback<\/h3>\n\n\nClick “Confirm”<\/strong>: The modal closes, the list refreshes immediately, showing all successfully added IPs (including those already existing, which are not duplicated).<\/p>\n<\/li>\n \nNo matter how many IPs are added in one batch, each IP appears as a separate record<\/strong> in the list for easy individual management.<\/p>\n<\/li>\n \nClick “Cancel”<\/strong> to close the modal without performing any action.<\/p>\n<\/li>\n<\/ul>\n <\/p>\n \nPropagation delay notice<\/strong>: After successfully adding an Whitelist entry, it may take up to 2 minutes<\/strong> to take effect globally. During this period, the new configuration may not yet be fully synchronized to all edge nodes. Please try again later.<\/p>\n<\/blockquote>\n <\/h2>\n4. Deleting an IP from the Whitelist<\/h2>\n\n\nFind the IP to delete in the list and click the “Delete”<\/strong> button in its row.<\/p>\n<\/li>\n \nA confirmation dialog appears:<\/p>\n<\/li>\n \nClick “Confirm”<\/strong> to remove the IP from the Whitelist; the list will refresh automatically. Click “Cancel”<\/strong> to abort the deletion.<\/p>\n<\/li>\n<\/ol>\n <\/p>","pure_content":"he IP Whitelist feature allows you to designate a set of trusted IP addresses. Only registration or login requests originating from these IPs will be permitted. Once the Whitelist is enabled, any IP not on the list will be denied access, effectively enhancing your application's security.\nPath: Console \u2192 Enter a specific application \u2192 Left navigation\u300cConfiguration\u300d\u2192 \u300cSecurity Settings\u300d\u2192 \u300cRisk Policies\u300d\u2192 Select\u00a0\u201cIP Whitelist\u201d\u00a0tab\n\u00a0\n1. Feature Overview\n\n\nIP addresses in the Whitelist are permitted to perform registration and login operations (the restriction type is fixed as \u201cAllow registration\/login\u201d).\n\n\nWhen processing a request, the system checks the blacklist first, then the Whitelist.\n\n\nIf the IP is on the blacklist, it is directly rejected.\n\n\nIf the IP is not on the blacklist but the Whitelist is configured (at least one entry), then only IPs on the Whitelist are permitted; all other IPs are rejected.\n\n\nIf the Whitelist is empty (no IP configured), then no Whitelist restriction applies \u2013 all IPs are allowed (though they are still subject to blacklist checks).\n\n\n\n\nAll configurations are managed per application and are independent of each other.\n\n\n\u00a0\n2. Whitelist List Page\nThe list page displays all added IP Whitelist entries in a table, supporting search and pagination.\n\n\n\n\n Field\n Description\n Example\n\n\n\n\n IP\n The permitted IP address\n 183.6.116.162\n\n\n Restriction Type\n Fixed as \u201cAllow registration\/login\u201d\n Allow registration\/login\n\n\n Added Time\n Time the record was added, format\u00a0YYYY-MM-DD HH:mm:ss, automatically converted to your browser's timezone\n 2026-04-02 11:05:51\n\n\n Actions\n A \u201cDelete\u201d button to remove the IP\n [Delete]\n\n\n\n\nList operations:\n\n\nSearch: A search box at the top left of the list supports fuzzy search by IP address.\n\n\nAdd IP: The\u00a0\u201c+ Add IP\u201d\u00a0button at the top right of the list opens an add modal.\n\n\n\n3. Adding an IP to the Whitelist\nClick the\u00a0\u201c+ Add IP\u201d\u00a0button to open a modal for entering the IP addresses to be allowed.\n3.1Form fields\n\n\n\n\n Field\n Description\n Required\n Rules\n\n\n\n\n IP\n IP address(es) to add to the Whitelist\n Yes\n Supports a single IP (e.g.,\u00a0123.45.67.89) or multiple IPs separated by\u00a0English commas\u00a0(e.g.,\u00a0123.45.67.89, 203.0.113.5). Maximum of\u00a0100\u00a0IPs per batch.\n\n\n Restriction Type\n Fixed as \u201cAllow registration\/login\u201d, not changeable\n Yes\n \u2014\n\n\n\n\n3.2Validation rules\n\n\nFrontend real\u2011time validation: Checks each IP format and correct comma separation. If invalid, an immediate prompt is shown (e.g., \u201cPlease enter a valid IP address\u201d).\n\n\nBackend duplicate check: After submission, the system processes each IP individually. Any IP already on the Whitelist is\u00a0automatically skipped without duplication\u00a0and\u00a0no user notification\u00a0is shown. Only new IPs are successfully added.\n\n\n3.3Saving and feedback\n\n\nClick\u00a0\u201cConfirm\u201d: The modal closes, the list refreshes immediately, showing all successfully added IPs (including those already existing, which are not duplicated).\n\n\nNo matter how many IPs are added in one batch, each IP appears as a\u00a0separate record\u00a0in the list for easy individual management.\n\n\nClick\u00a0\u201cCancel\u201d\u00a0to close the modal without performing any action.\n\n\n\n\nPropagation delay notice: After successfully adding an Whitelist entry, it may take up to\u00a02 minutes\u00a0to take effect globally. During this period, the new configuration may not yet be fully synchronized to all edge nodes. Please try again later.\n\n\u00a0\n4. Deleting an IP from the Whitelist\n\n\nFind the IP to delete in the list and click the\u00a0\u201cDelete\u201d\u00a0button in its row.\n\n\nA confirmation dialog appears:\n\n\nClick\u00a0\u201cConfirm\u201d\u00a0to remove the IP from the Whitelist; the list will refresh automatically. Click\u00a0\u201cCancel\u201d\u00a0to abort the deletion.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1775470498","update_time":"1779162320"},"pure_content":"he IP Whitelist feature allows you to designate a set of trusted IP addresses. Only registration or login requests originating from these IPs will be permitted. Once the Whitelist is enabled, any IP n"}],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}