Many clients put Wifi's actual name certification system and Portal authentication together when the project started to communicate, even directly admitting that it was the same thing. The most common thing to hear at the site is:“We already have Portal. Can we get a page to authenticate?”On the surface, this understanding seems to be not problematic. Is it a real name authentication?
And the problem is that when you get to the project, it's usually starting here. Because normal Portal certification and a real-real Wifi authentication system are not really an aspect of this. Portal is more like“Import”The Wifi physical name certification system is a set of programs for authentication, management, marking, and control. The entrances are popping out without the integrity of the authentication chain; pages are showing that the back-office account systems, access controls, log retention, visitor differentiation, equipment compatibility are all available. Many projects start with mixing the two, the need is simple in the first place, and the bottom line is always filled with holes.
Portal authentication is essentially a web-based certification mechanism. Once the user has access to wireless networks, the system redirects user requests to an authentication page where it completes login, confirmation, click release and so on, and then the network side decides whether to allow them to be allowed to do so according to the authentication results. Its biggest feature is that the front end is clearly visible, and users can see one page directly. Many equipment manufacturers also advocate their support for Portal, so many customers naturally feel that they have a physical system that supports Portal.
Here's the problem. Portal page is just the level that users see, and it solves the problem.“How do you get a user to an authentication entrance?”This is a problem. The project really needs to be addressed more than that. One unit does not actually use Wifi name certifications for the purpose of playing a page that looks good, or for users to confirm it more often, but rather to know who is online, by what means, when, how access should be divided, whether the log can check, whether visitors and employees can distinguish between management and unusual behaviour, and whether they can't do it back up. These are elements that cannot be solved by just one Portal page.
The real Wifi authenticated system first addresses the identity problem. Who are employees, who are visitors, who are temporary guests, who are hotel guests, who are partners in the campus, and who may be certified differently. That is, the real Wifi authenticated system does not just give everyone a single page but calls different authentication logics according to identity type and connects the certification results with the back-office management system.
It does not necessarily have a complete identity grouping capability, nor a fine-tuning competency management capacity, much less a division of staff, visitors, temporary users, and partners. The problem arises when it comes to the real project environment. Staff members are expected to avoid repeated accreditation for a long time, visitors are allowed to travel only temporarily, access is restricted in some areas and certain user logs are kept separately, which means that a normal Portal page is simply not available.
The second difference is authenticity and scarmability. Many clients think that a real-name authentication is not so simple as long as the user fills in a cell phone number or clicks on a micro-entry. Really meaningful Wifi real name certification system, which does not just allow users to fill out an information, but rather allows authentication and identification, Internet-based binding, and log logging. More directly, the system needs to know who has successfully certified it by what means, at what time, with which end, from which point of access, through which link to which web link, and whether it can be found back up and back when checking logs. This is the real name authentication that really counts in the project.
And normal Portal certification, often just“Looks like it's certified.”. Users enter something, the page is passed and the web is released, but the back desk records are thick, leaving even a simple account or cell phone number. When there is a problem back there, checking authentication records, corresponding logs, matching user identities is often not correct or complete. This difference is particularly evident in hotels, parks, office buildings, public places. If you want to be on schedule, it will be possible to play a page, and the more you use it, the less you can find it.
The third difference is in network control. Portal certifies pages that many people see, and professional projecters view links. Because users see pages that really determine whether they can be secure, controlled, or left visible, it is the logic of network control that follows. A truly mature Wifi real name authentication system usually combines with wireless accelerator, switchboard, Natshell_GATEWAY, Radius, Log Audit, etc. After authentication is successful, there are stabilization mechanisms for how users are released, how permissions are given, how equipment is maintained online, how users are treated when they turn off, and how anomalies are re-certified. This is not a page, a cell phone number, but the connection is naturally established.
The problem with many of the ordinary Portal programmes is that it only solves page jumps, but does not establish a back-end control link. So, the result is that the pre-destination is no problem, and when users come up, things start to happen: some people certify success without access, others just authenticate and jump back into the login, someone switch over to the area and repeat it, some pages can play but access the outer network continues to fail, and pages open at peak terminals when they are simultaneously connected to them is clearly slower. These problems appear to be web issues, often because the scheme has only Portal and does not really have a full Wifi real name certification system.
There is also one thing that customers can easily ignore: compatibility. Many sites already have wired devices, perhaps Chinese, or sharp, maybe Chinese, or other brands. Clients usually ask first:“Do we have aAC support for the docking?”If it is just a normal Portal idea, the answer is often random, thinking that you can play a page as long as you can. The real projecter does not judge that. Because of the ability to match, not whether or not the page will be played, it is to see if existing equipment supports external Portal, Radius' capacity, whether authentication links are connected, if export locations are suitable for authentication controls, how to keep a log, and whether visitors and employees can divide strategies.
And because of that, many projects appear to be.“Portal”In practice, when actually landing, there is often a need for Authentication Gateway or additional control nodes. In particular, some equipment that supports Portal page jumps but has limited ability to connect with external certification systems, and if it is maintained as a complete real name authentication system, the back of the site will be in trouble.
Ordinary Portal certifications are more like a front-end portal tool, and Wifi's real name certification system is the management system. What does it mean that the management system means that backstages can build rules, role-sharing, strategy, log reading, permissions, records check, online statistics, and, if necessary, differentiated controls by department, region, type of user. For example, business office scenes, staff and visitors should not be allowed to follow the same authentication process or access; hotel scenes make it more difficult for tenants and internal carriers to share a set of strategies; The range of time and release is often different for fixed office users, construction workers, temporary visitors, and partners.
The difference between the two is also important from a procurement perspective. Because many clients thought that Portal was cheap, that it had been done on the page, and that advertising was available, that demand would be almost enough.
So the biggest difference between the Wifi real name certification system and ordinary Portal authentication is not about how long the page looks, nor where the authentication buttons are placed, but about whether there is a complete authentication logic, identity system, network control, log retention, permission management and system interface. Portal can be part of the real name certification system, but it does not itself amount to a real name certification system.
Many projects have been poorly followed, not by technology, but by a mix of concepts. For most units, the page is just an entry point and really determines whether the project can be sustainable over time or whether it remains a full Wifi real name certification system.