Dynamic Access Token Switching for OPC Connection Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Open Process Control (OPC) systems, connection failures often occur due to mismatched token credentials between OPC clients and servers, especially when the proxy connection and server are not in the same domain, or when the server does not support the specific token used, leading to failed access to industrial hardware devices.
Innovation Solution
A client computer system with a connection failure recovery program dynamically changes access token types by initiating a session with a first token type and, if the request fails, switching to alternative token types such as a username/password token or an anonymous token, stored on a machine-readable storage medium, to establish a connection with the target server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a client uses a specific token type to connect to a server, then the connection may be established if the token is compatible, but the connection fails when the server does not support the specific token or when domain mismatch occurs
Solution Approach 1:
The system dynamically switches between different token types based on connection success or failure. The client initially uses a first token type (e.g., client security token) and upon connection failure, automatically switches to alternative token types (e.g., username/password token, anonymous token). This dynamic adaptation resolves the contradiction by making the connection process flexible rather than static, allowing the system to adapt to different server configurations and domain environments.
Solution Approach 2:
The system changes the token type parameter when connection fails. Instead of using a fixed token type, the client modifies the token parameter by switching to different authentication methods. This parameter change allows the system to overcome token compatibility issues and domain mismatch problems, thereby improving connection reliability without requiring the server to support every possible token type.
2Adaptability or versatility
If the proxy connection and server are not in the same domain, then network flexibility is improved, but token credential mismatch occurs causing connection failure
Solution Approach 1:
The system uses alternative token types as intermediaries to bridge the authentication gap between proxy connections and servers in different domains. When the first token type (client security token) fails due to domain mismatch, the system employs other token types (username/password, anonymous) as intermediary authentication mechanisms. This allows the system to maintain network configuration flexibility while overcoming authentication failures across domain boundaries.
3Reliability
If multiple token types are tried sequentially, then connection reliability is improved, but connection establishment time increases
Solution Approach 1:
The system performs preliminary actions by maintaining multiple token types ready for use before connection attempts. Instead of generating or searching for alternative tokens when needed, the client keeps different token types (client security token, username/password token, anonymous token) pre-configured and ready. This preliminary preparation reduces the time penalty of token switching, as the system only needs to switch between pre-available options rather than creating new authentication credentials during connection attempts.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system for dynamically changing access tokens in a communication system (100). A client computer system (110) is communicatively coupled by a communication channel (139) to at least one target server (160). The client computer system includes a processor (202) connected to a storage device (216) that has a non-transitory machine readable storage medium (222). The storage device stores a connection failure recovery program (318). The client computer system is programmed to implement the connection failure recovery program. The client computer system initiates a session (140, 142, 144) by transmitting a first request for a connection (406) to the target server using a first token type (312) such as a client security token and if the first request fails, transmits a second request for a connection (412) to the target server using a different token type (314).