The backend entry of the public trial site can be tried at will, and how to narrow the login page of your own site
The back-end entry of the public demo station can be tried at will, and how to narrow the login interface of your own site, the answer is to narrow it in three layers: entry exposure method, account permission boundary, and machine behavior protection. The value of the demo station (demo site) lies in allowing people to see the functions without entering the back-end; copying this level of openness for a self-built site with real data and real accounts will bring back the area that can be tried.
Why does the demo station need to open the back-end entry
AnQiCMS provides an online experience site, the background address is fixed at /system path, the role of this demonstration entry is to reduce the threshold for trial: people who want to see the effect do not need to deploy first, nor do they need to apply for an account first. The demonstration site contains sample content and sample accounts, and the changes affect others' browsing, not the production data. It is precisely this premise that makes the 'public entry' acceptable. On the other hand, once the site contains real orders, real member information, and real attachments, the same degree of openness is no longer equivalent.
What are the ways to expose the entry step?
There are three options for exposure, with risks arranged from low to high: whether the path is guessable, whether to allow unlogged-in access to the login page, and whether to add access restrictions to the entry. A fixed path is convenient to use and also easy for scanners to hit, so it is common practice to keep a memorable address for the team on the self-built site instead of following the default address of the demonstration site. Site-wide operations (backups, upgrades, multi-site management) are high-risk actions, and the exposure range of such capabilities is closed by default, and it needs to be explicitly enabled to be available externally, which is exactly opposite to the orientation of the demonstration site "showing everything to everyone."
Which layer should the user group and VIP group be collected first
The way to control the boundary of authority is to group first and then give the scope, instead of assigning it individually to each person. User management supports division by user group, and VIP grouping can set different access permissions for different groups, downloading range, visible content, and background menus are all condensed by group. Operation, editing, and external proxy maintenance fall into different groups, and the interface that can be seen is naturally different: the account for writing articles does not need to be able to change the template, and the account for accounting does not need to be able to delete documents. This level is first tightened up, even if the login credentials are leaked at some stage, the range of capabilities that can be used is also blocked by the group boundary.
Who controls the machine behavior at the form and login ports?
Machine behavior protection is divided into two places: login port and external forms. Forms such as messages, orders, and subscriptions can be connected to reCAPTCHA verification codes to block repeated submission scripts before writing to the database; the login port relies more on the authentication mechanism itself, AnQiCMS has built-in JWT authentication, the session status is maintained by tokens, and attempts of abnormal login will not be replaced by a long-term valid credential. The verification code is placed on the side of the form to solve flooding, and tokens and permission groups are placed on the back-end side to solve over-privilege, and the two do not substitute each other.
Why is the content layer protection also considered as a login page?
Behind the back-end entry, there is also a layer that is easily overlooked: the procedural entry. SQL injection and XSS take advantage of holes outside the login interface to enter the system, and built-in filtering and protection are responsible for this section; sensitive word filtering and keyword replacement in content security settings, interference codes to prevent collection, belong to the content layer rather than the authentication layer, but they determine whether external submissions can rewrite data within the site. If the upgrade action is to fix this type of entry, the upgrade action itself is also part of narrowing the login interface.
How to allocate the three layers, which one to look at first
| Hierarchy | The approach of the experience site | The tightening action of the self-built site | The order of what to do first |
|---|---|---|---|
| Entry exposure | Fixed address is public, convenient for direct viewing | Replace the default address visible to the outside, keep the default closed at the whole site level | First step, the lowest cost of change |
| Permission boundary | Public trial account, all features are open | Divide the access range according to user groups and VIP groups, one person per group | Second step, decide the radius of impact after leakage |
| Machine behavior | Unrestricted, allow repeated attempts | Form accepts reCAPTCHA verification code, login relies on JWT token and session control | The third step, blocking automated attempts |
Common questions
Changed the back-end entry address, will the editor not be able to enter?What will change is the access path, not the account and permissions. Send the new address to the internal collaboration group in advance, and finish updating the bookmarks, and the transition period is over once.
The site is maintained by only two people, do we need to group?Yes, but only two groups: those who can change content and those who can change settings. The purpose of grouping is not the approval process, but to limit the scope of impact after accidental operations and credential leaks.
Will the captcha affect the normal user's submission?The cost of reCAPTCHA on the normal submission path is a single verification, comments and order forms can be opened as needed; if real human submissions are blocked, check the form integration method first, and then decide whether to open up or retain.
Can the public entry of the demonstration site be directly copied to your own site?It is not recommended. The public of the demonstration site is a product behavior, the premise being that there is no real data; the data, accounts, and orders of the self-built site are all real, and the same entry exposure does not have the same premise.