Portal Device Management via Capability Negotiation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web authentication techniques in campus networks face issues such as portal clients being unable to sense server load, requiring manual configuration changes for IP address updates, and needing synchronous protocol upgrades, leading to complex operation and maintenance, as well as security concerns with encryption key management.
Innovation Solution
Implementing a portal device management method that uses capability negotiation between portal clients and servers to establish and maintain instance connections, allowing for smooth protocol upgrades, load balancing, and secure operation by announcing information and using asymmetric encryption, thereby simplifying maintenance and enhancing security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual configuration changes are made on the portal server side when IP address pool changes, then the portal client and portal server can maintain consistent configuration, but the operation and maintenance becomes tedious and complex
Solution Approach 1:
The portal client automatically discovers and obtains IP address pool information from the portal server through capability negotiation and information announcement mechanisms, eliminating the need for manual configuration changes on the server side when IP addresses change
Solution Approach 2:
The portal server announces its information including IP address pool to the portal client, creating a feedback mechanism where the client receives real-time updates about server configuration changes without manual intervention
2Reliability
If synchronous upgrading is performed on the portal server and portal client when upgrading portal protocol, then protocol compatibility is maintained, but the operation and maintenance becomes tedious and complex
Solution Approach 1:
The system implements dynamic capability negotiation between portal client and server, allowing them to automatically determine compatible protocol versions through negotiation rather than requiring synchronous manual upgrades, making the system adaptable to different protocol versions
Solution Approach 2:
The portal client and server automatically negotiate and establish instance connections based on their respective capabilities and protocol versions, eliminating the need for manual coordination during protocol upgrades
3Reliability
If symmetric encryption key configuration is performed manually on both portal server and portal client, then security is achieved, but the operation and maintenance becomes tedious and complex
Solution Approach 1:
The system transitions from symmetric encryption to asymmetric encryption (public key infrastructure), where the portal server holds private keys and portal clients use public keys, eliminating the need for manual symmetric key configuration while maintaining security
Solution Approach 2:
The asymmetric encryption keys are automatically configured and managed by the system through capability negotiation, eliminating manual key distribution and configuration between server and client
4Ease of operation
If the portal client selects a portal server with simple processing logic, then the client can easily implement server selection, but the client cannot sense the server state or accept load sharing indications, leading to authentication failures when the server is busy
Solution Approach 1:
The portal server announces its state information including load status to the portal client, enabling the client to sense server conditions and make informed selection decisions, while the server can also receive and respond to client requests appropriately
Solution Approach 2:
The capability negotiation mechanism serves multiple functions: establishing instance connections, exchanging state information, enabling load balancing, and supporting protocol version matching, all within a single unified process
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Disclosed is a portal device management method, and the method includes: an instance connection between a portal client and a pre-configured portal server is established through capability negotiation; and each of the portal client and the pre-configured portal server having the instance connection established therebetween announces its information to its opposite end. Further disclosed are a portal device and a portal system, in the embodiments of the disclosure, an instance connection is established between a portal server and a portal client, and load balancing of the portal server is implemented based on the established instance connection; it is possible to solve the problem that the portal client and the portal server cannot upgrade smoothly; information such as a public key of an asymmetrical algorithm and an IP address pool can be automatically announced between the portal client and the portal server without manual configuration operations, thereby result in convenient and secure operation and maintenance.