Search
15 result(s) for authenticationToken
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesRequestHeader structure is defined in 7.32 and contains common request parameters such as authenticationToken , timestamp and requestHandle . The ResponseHeader structure is defined in 7.33 and contains common response parameters such
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.2.2 ParametersFindServers Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The authenticationToken shall be ignored if it is provided. The type RequestHeader
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.3.2 ParametersFindServersOnNetwork Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The authenticationToken shall be ignored if it is provided. The type RequestHeader
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.4.2 ParametersGetEndpoints Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The authenticationToken shall be ignored if it is provided. The type RequestHeader
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.5.2 ParametersRegisterServer Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The type RequestHeader is defined in 7.32 . Server RegisteredServer The Server to register
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.5.6.2 ParametersService . Table 8 - RegisterServer2 Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The type RequestHeader is defined in 7.32 . Server RegisteredServer The Server
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.6.2.2 ParametersOpenSecureChannel Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The type RequestHeader is defined in 7.32 . clientCertificate ApplicationInstanceCertificate A Certificate that identifies
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.6.3.2 ParametersCloseSecureChannel Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The type RequestHeader is defined in 7.32 . secureChannelId BaseDataType The identifier
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.7.2.1 Descriptionaudit logs and in the Server's AddressSpace . The second is the authenticationToken which is used to associate an incoming request with a Session . Before calling this Service , the Client
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.7.2.2 ParametersCreateSession Service Parameters Name Type Description Request requestHeader RequestHeader Common request parameters. The authenticationToken is always null. The type RequestHeader is defined in 7.32 . clientDescription Application Description Information that describes ... Audit logs and their related events are described in 6.5 . authentication Token Session AuthenticationToken A unique identifier assigned by the Server to the Session . This identifier shall be passed
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services5.14.7.1 Descriptionover a Subscription from another Client by transferring the Subscription to its Session . The authenticationToken contained in the request header identifies the Session to which the Subscription and MonitoredItems shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services6.3.1 DescriptionSecureChannel using the Access Token returned from the Authorization Service as the authenticationToken in the requestHeader. The SecureChannel shall have encryption enabled to prevent eavesdroppers from seeing the Access Token ... require the Access Token and assume an anonymous user. In this case the authenticationToken shall be null. The SessionlessInvoke Messages are just an envelope for the Service to invoke
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model3.1.1 ClientUserIdUserIdentityToken passed by the Client in the ActivateSession Service call or from the authenticationToken in the requestHeader of a SessionlessInvoke Service call. See 6.4.3 for details
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappingsrenewed before the RevisedLifetime expires. Receivers shall still ignore invalid or expired TokenIds. The AuthenticationToken in the RequestHeader shall be set to null. If an error occurs after the Server
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings7.4.1 Overviewwith a SecureChannel. This means that Sessions can only be considered secure if the AuthenticationToken (see OPC 10000-4 ) is long (>20 bytes) and HTTPS encryption is enabled ... implementation dependent. HTTPS connections have an unpredictable lifetime. Therefore, Servers must rely on the AuthenticationToken passed in the RequestHeader to determine the identity of the Client . This means the AuthenticationToken