The netting system Authentication & Billing directly determines whether the system is connected to the operating systems that are already in place at school."It works."Or..."It's working.". If the certified account requires a student to register separately, the net charge is worth going to a cartoon centre to pay for it and the check-out number will not automatically be cancelled——The Authentication & Billing system, like this, does not feel useful to the information centre even if it is functional. But the technical route for getting through this is wrong, and the data synchronization and state consistency issues between all the systems that follow are going to roll up like snowballs.
The core need for the interface with the teaching system isAutomatically sync up to teacher/student identification dataEvery September, when new students enter the school system, thousands of student records are added to the teaching system; several thousand more records have to be marked off as missing each June. NATSHEL_AUTH_BILLING must automatically feel these changes, otherwise it becomes a reality."Information Islands". The current mainstream technology route is two: one is the LDAP directory sync, and the NATSHEL_AUTH_BILLING system regularly (e.g. every 30 minutes) updates user data from a school LDAP server; the other is the API interface docking, where the teaching system actively transmits events to Authentication & Billing when the user changes.
The advantage of the LDAP program is thatImplementation of simple, non-intrusive teaching systems——The data can be pulled only by configuration of the LDAP server connection parameters and query filters. But the disadvantage is that synchronisation sometimes delays, and in extreme cases a new registered student may have to wait 30 minutes to log in on the NATSHEL_AUTH_BILLING system. If this student just returns at night to register the network fees and finds that there are no accounts, it's bad experience. And LDAP synchronization for LDAP is not possible."Delete"and"Freezing"The two states are rough.——If the teaching system is only marked on a field,"Graduated"Instead of actually deleting records, LDAP syncs may not correctly reflect this state change.
API docking program is achievablePre-real time sync——The teaching system calls the Authentication & Billing interface to push events when user status changes. However, this program requires a higher degree of adaptation of the teaching system——Many schools have a system of learning products purchased many years ago, without an API interface or with interfaces but very limited capabilities (e.g. full-scale export and non-republishable). In such cases, the API docking programme is effectively equivalent to secondary development by SMS manufacturers, with cycles and costs being uncontrollable.
The connection to a cartoon system is another challenge:The payment chain is connected.. Students select a set of meals, clicks to fill the system in Authentication & Billing, and backend calls a cartoon payment interface to deduct money from student accounts, and after deduction is successful NATSHEL_AUTH_BILLING has introduced matching suite privileges. This process involves two systems for account consistency.——A cartoon deduction was successful but the Authentication & Billing system was not operational, students were paid but could not access the Internet; or, conversely, a card-to-ton deduction failed.
Standard approach to resolving consistency of accountsTwo-part business.. But many campus-toon interfaces do not support a full rollback mechanism——The payment interface is..."Call and deduct."No, I didn't."Pre-detention + confirmation". In this case, the Authentication & Billing system will have to perform a compensation mechanism: recording a payment stream after deduction has been successful and then trying to open a package, automatically initiating refunds or generating an pending worksheet if opening fails. Also, daily reconciliations at the system level will be performed——The nettle-to-line recording of the Authentication & Billing system and the deductions from a cartoon system are matched by daily, article by article, with manual intervention when discrepancies are detected.
The interface of the UID platform is relatively simple——In essence.Connect the NATHHELL_AUTH_BILLING system as a SP (Service Practice) to the CAS or OAuth single-point login system of schools. The students jump to the Portal page of NATSHEL_AUTH_BILLING after a uniform accreditation platform has been registered. This match is conditional on the school ' s unified identity card platform being built and stable. If schools do not have a single CAS/OAuth platform, this step can be jumped and supplemented.——The lack of uniform authentication does not affect the operation of core functions in Authentication & Billing.
And there's another constant missing connection demand:Electronic resources access to the LibraryThe Internet is used by operators instead of the school network, which leads to students being judged as IP in databases."Out-of-school users". This problem requires the allocation of export strategy routes on dial-up gateways——The flow of access to the academic database target IP section takes out the school education network instead of the operator. But this strategic route is not very expensive to maintain.——The IP section of the database manufacturer is subject to change and needs to be updated regularly.
All these key success factors of the interface are summarized as follows:Clear inventory of all required systems during the start-up phase of the project, assessing the interface approach, interface capacity and implementation difficulties on a case-by-case basis. Do not suddenly find out during the project"Oh, yeah. And we're gonna have to get back to that system.", the entire schedule and resource allocation will have to be re-routed."Additional development is required"Don't assume that"There should be an interface."。