Many schools have been placed in wireless Portal, and students still have to keep two sets of accounts, one school number, one Internet account, and a code change on both sides. The ideal state for wireless Portal is to eat the school's uniform identity, so that students can go to WiFi with their student code. This is done, and the students simply don't know about the system.
Why do you have to match the same identity?
If not, the network center will maintain a number of accounts itself. The students forget to replace you with the code and they will have to sell it manually. The matching identity, the old and the dead account, follow the teaching and personnel systems, and the network centre will only certify that the account is not valid. We've counted a sum of money. A million schools do not have thousands of copies of the annual resets of light codes, which are largely zero.
Reconciliation: standard protocol or interface
The usual standard-of-separation protocols, with the school ' s unified identity platform as a back-up source of forensics, have wireless Portal only perform front-end presentations and maintain conversations. There are schools that use their own interfaces to match them, flexible but costly to maintain. We suggest that they should be preferred to standard agreements, where manufacturers support them well and replace them without kidnapping. If the school ' s unified identity platform is older, it may need to be added to the appropriate gateway, which needs to be evaluated in advance.
Password Sync and Decrypt Experience
The most visual benefit is a password-based change. Pay attention to the modified session: students change their passwords, and whether the currently registered WiFi session is maintained or reconnected, which should be the case. We generally recommend that a grace period be given when the secret is changed so that the equipment in use can be smoothly transitioned instead of kicking down immediately to trigger a wave of complaints.
Multi-source processing
Schools are not just for students, but also for teachers, temporary visitors, and partners. The source of identity may be different systems. Wireless Portal is able to match with different sources, giving different access rights and lengths. We suggest that the list of sources be drawn up before we go online, and rules are set on which to take a unified identity, which to take a provisional account, and how to issue short-term certificates.
Descending Program for Failed Reconnection
A good match will also be made against a single-hand UID platform. We usually ask Portal to keep a local cache, allowing students to access the Internet for a few minutes instead of a complete break when the UIS is temporarily unavailable. This cache is time-bound and the platform will be rechecked as soon as it is restored. The downgrade is not intended to bypass certification, but to avoid single malfunctions that drag the entire building down.
Reciprocal self-service
After a unified identity, students should use the school ' s single self-help portal instead of searching for a single network. We suggest that the self-service capability of an online account be placed on a single identity self-help page, where students can handle all accounts related matters. Self-help is open and the reloading list at the network centre is almost zero, and students do not have to run windows to change their passwords. Half the value of the switch is free of maintenance and half is self-help.
We need to clear the border.
The answer is based on the principle that wireless Portal only gives a test, without passwords, and all password verifications are given to the single identity platform. We have seen schools using a local password for the purpose of saving the use of certification systems, which are notified when checking them. Passwords can be used in one place, or as an identification source. Authentication systems have access to proof of pass, not to a code.
Surveillance of the link.
The feeder is not finished, but the link itself has to be looked at. We suggest monitoring the UID to wireless Portal for delay and success, so that the platform shakes and students are slow to log in. By pulling this indicator alone, it will be possible to find problems half a day before the student complains. Many schools focus on the certification system themselves, forgetting that the upstream identity platform is also connected, and the platform is shaking and not knowing the pot.
Reciprocal document to be kept bottom
The docking protocol, the source list, and the downgrading process end up in a page of documents for later generations. We've seen the same teacher who moves away and the new one gets tangled into the system. The files are left behind, hand-overs and troubleshoots fast.
The problem is solved by using the student code to access the Internet and improve the automatic synchronization of complaints. The only truth is that, with a single identity, Portal is the consumer on the wireless, and there are protocols, passwords, multi-identity sources, downgrading programs, which will be easier. The switchback is a one-time input, and long-term savings, which will be considered as a good sum.