Search

Scope: Core (OPC-10000-*) All specs

93 result(s) for Sessions

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

4.4.1.2 Discovery and Session establishment

established. The mechanisms for discovering Server s and establishing secure communication channels and application Sessions are described in OPC 10000-4 and OPC 10000-6 . Additional information about the Discovery
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

4.5 Sessions

Sessions OPC UA ClientServer interaction requires a stateful model. The state information is maintained inside an application Session . Examples of state-information are Subscriptions , user credentials and continuation points ... operations that span multiple requests. Sessions are defined as logical connections between Clients and Servers . Servers may limit the number of concurrent Sessions based on resource availability, licensing restrictions
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.2.8 Availability

appear as slowing down of Subscription performance or the inability to add Sessions for example
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.2.2 Message flooding

which it does. Message flooding can impair the ability to establish OPC UA Sessions or terminate an existing Session . In the second scenario, an attacker could use a malicious Client
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.3.2.3 Resource Exhaustion

Clients from accessing the Server . For example, on a Server in which only 10 Sessions are available a malicious person using a legitimate Client, could obtain all 10 Sessions
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.5.2.2 Session application layer

activated before it can be used, the binding of users, Sessions , and SecureChannels is flexible. Impersonation allows a user to take ownership of an existing Session . If a SecureChannel breaks
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

5.2.8 Availability

Message flooding as described in 5.1.2 . Some attacks on Availability involve opening more Sessions than a Server can handle thereby causing the Server to fail or operate poorly. Servers reject ... Sessions that exceed their specified maximum number. Other aspects of OPC UA such as OPC UA Secure Conversation can also affect availability and are discussed
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.9.3 Evaluating Permissions with Roles

rules defined for each Role . Table 5 lists the assigned Roles for different Sessions created with different Users , Client applications and Endpoints . Table 5 - Example Role Assignment User Provided
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.2 NodeId

references. A Server may change the namespaceIndex NodeId element of a Node with future Sessions and therefore a Client shall not assume the namespaceIndex will not change. The structure
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

5.2.10 UserRolePermissions

this Attribute is derived from the rules used by the Server to map Sessions to Roles . This mapping may be vendor specific or it may use the standard Role model
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

4.1 Service Set model

Client to authenticate the user on whose behalf it is acting and to manage Sessions . Figure 3 - Session Service Set The NodeManagement Service Set , illustrated in Figure 4 , defines Services
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.5.4.1 Description

security is NONE then it is possible for Clients to deliberately or accidentally hijack Sessions created by other Clients . A Server may have multiple HostNames . For this reason, the Client
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.7.2.1 Description

associate a new SecureChannel with the Session by calling ActivateSession. For the N Sessions supported by a Server, the Server shall support N+1 SecureChannels . A Server may support multiple ... Sessions for one SecureChannel . The SecureChannel is always managed by the Communication Stack which means it shall provide APIs which the Server can use to find out information about
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.7.2.3 Service results

this result code. Bad_TooManySessions The Server has reached its maximum number of Sessions . Bad_ServerUriInvalid See Table 178 for the description of this result code. Bad_SecurityPolicyRejected See Table
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.7.3.3 Service results

mainly available to change the password. The detailed definitions for UserManagement , restrictions for Sessions and the Method ChangePassword used to set a new password are defined
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.14.1.1 Description

with the status code Bad_Timeout. The StatusChangeNotification notificationMessage type is defined in 7.25.4 . Sessions maintain a retransmission queue of sent NotificationMessages . NotificationMessages are retained in this queue until they
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.6.2.3.2 Server requirements

ServerUri shall not change. The Client shall be able to continue communication with the Sessions and Subscriptions created on the previously used Server . Figure 26 provides an abstract view
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.6.2.4.4 Server Failover modes

more than one Server can be active and fully operational. Mirroring state minimally includes Sessions , Subscriptions , registered Nodes , ContinuationPoints , sequence numbers, and sent Notifications . The ServiceLevel Variable defined
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.6.2.4.5.5 HotAndMirrored

validate the capability to connect to other redundant Servers it is allowed to create Sessions with other Servers and maintain the open connections by periodically reading the ServiceLevel . A Client
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.6.4.3 Non-Transparent

described in 6.7 can be used. Only the SecureChannel is created with another Endpoint . Sessions and Subscriptions can be reused. Non-transparent network Redundancy is illustrated in Figure 35 . Figure
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

6.8 Durable Subscriptions

SetSubscriptionDurable Method defined in OPC 10000-5 to create a durable Subscription Close Sessions for planned communication interruptions Use the Service TransferSubscriptions to assign the durable Subscription
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.35 SessionAuthenticationToken

NodeId with a UInt32 identifier that allows the Server to distinguish between different Sessions created by the same sender. In some cases, the application and the Communication Stack cannot exchange
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.2 ServerCapabilitiesType

MaxSessions is an unsigned integer specifying the maximum number of concurrent Sessions the Server can support. The value specifies the maximum the Server can support under normal circumstances, therefore there
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.5 SessionDiagnosticsObjectType

Server has granted to the current Session . Since this information is security-related, Sessions other than the current Session shall be restricted to authorized users, such as users who have
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.8 TransparentRedundancyType

This Server is valid only inside a Session ; if a Client opens several Sessions , different Servers of the redundant set of Servers may serve it in different Sessions . The value
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

7.1.5 Error handling

close the SecureChannel . For example, calling CreateSession on a SecureChannel that does not allow Sessions . The numeric values for these error codes are defined in A.2 . NOTE: The 'Tcp' prefix
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

7.4.1 Overview

SecureChannel which allows applications correlate a request with a SecureChannel. This means that Sessions can only be considered secure if the AuthenticationToken (see OPC 10000-4 ) is long
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

5.1 Overview

allow Servers to call the RegisterServer or RegisterServer2 Services . The LocalDiscoveryServer does not support Sessions so information needed for establishing Sessions , such as supported UserTokenPolicies , is not provided. In systems
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

6.2 Roles and Privileges

Session must have access to or by referring to Privileges which are assigned to Sessions using mechanisms other than the well-known Roles . The well-known Roles used
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

6.3 Client connections to global services

sequences. If it runs out of connection resources, a GDS is allowed to close Sessions with Clients which have not be authenticated as one of the GDS administrative Roles ... close Sessions , it should first close Sessions without GDS management Privileges . Otherwise, it may close the Session that was inactive for the longest time. It is also recommended
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.2 Roles and Privileges

Session must have access to or by referring to Privileges which are assigned to Sessions using mechanisms other than the well-known Roles . The well-known Roles used for CertificateManagers
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.8.2.5 CloseAndUpdate

TrustList changes the Server shall re-evaluate the Certificate associated with any open Sessions and SecureChannels. Sessions or SecureChannels with an untrusted or revoked Certificate shall be closed. This process
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.8.5.2 CloseAndUpdate

Updating the configuration will often require the endpoints to be closed and all active Sessions be interrupted. When the new configuration is applied it is possible that a configuration error ... wait before applying the configuration changes if applying the configuration changes will interrupt active Sessions . Clients set this value based on how long it takes for them to receive
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.10.2 Transaction Lifecycle

support exactly one active transaction. Once a transaction has started in Session all other Sessions will not be able to modify TrustLists or Certificates . Transactions are automatically cancelled when
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.10.9 ApplyChanges

Server Certificate and/or TrustLists. Servers may close SecureChannels without discarding any Sessions or Subscriptions. This will seem like a network interruption from the perspective of the Client and the Client
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

8.2 Roles and Privileges

Session must have access to or by referring to Privileges which are assigned to Sessions using mechanisms other than the well-known Roles . The well-known Roles used
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

9.2 Roles and Privileges

Session must have access to or by referring to Privileges which are assigned to Sessions using mechanisms other than the well-known Roles . The well-known Roles for an AuthorizationService
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

C.2 Client Server Subscriptions

Clients to access information provided by an OPC UA Server . Every Client creates individual Sessions , Subscriptions and MonitoredItems which are not shared with other Clients . In other words, the data ... that is published only goes to the Client that created the Subscription . Sessions are used to manage the communication relationship between Client and Server . MonitoredItems represent the settings used
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

4.3 RoleSet

IdentityCriteriaType.AuthenticatedUser . The Anonymous Role is the default Role which is always assigned to all Sessions . The Anonymous Role is the default Role which is always assigned to all Sessions
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

4.4.1 RoleType definition

indicates that the configuration of the Role and the assignment of the Role to Sessions is vendor specific. Roles are required to support the RolePermissions Attribute . If a Server want
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

5.2.6 ModifyUser Method

management of the Server. If the UserConfiguration bit Disabled is changed to TRUE, all Sessions and Subscriptions associated with the disabled user shall be closed by the Server
OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security

5.2.7 RemoveUser Method

used to remove a user from the user management of the Server . All Sessions and Subscriptions associated with the removed user shall be closed by the Server. The Client shall
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.6 Roles and Privileges

must have access to or by referring to named Privileges which are assigned to Sessions using mechanisms other than the well-known Roles . Privileges are needed because not all restrictions
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.13 DeviceRegistrationAuditEventType

Event and its subtypes are security related and Servers shall only report them to Sessions with access to the SecurityAdmin Role. Its representation in the AddressSpace is formally defined
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.14 DeviceIdentityAcceptedAuditEventType

Event and it subtypes are security related and Servers shall only report them to Sessions with access to the SecurityAdmin Role. Its representation in the AddressSpace is formally defined
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.15 DeviceSoftwareUpdatedAuditEventType

Event and it subtypes are security related and Servers shall only report them to Sessions with access to the SecurityAdmin Role. Its representation in the AddressSpace is formally defined
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-10101 – OPC UA for WoT Binding

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30060 – OPC UA for Tobacco Machine Communication

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30141 – OPC UA for PROFIenergy

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30142 – OPC UA for PROFINET Remote IO

4.3.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30142 – OPC UA for PROFINET Remote IO

6.7 OPC UA for RIO Security

Security Servers shall allow Method invocation and write access to Variables only for Sessions using dedicated user accounts. There shall exist user accounts with restricted rights (that is, no Method
OPC-30142 – OPC UA for PROFINET Remote IO

12.1 Conformance Units

Roles Server supports role-based security and restricts write access and method invocation to Sessions with granted "Operator" role. This includes support of the OPC UA "Security
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

6.6 Encoder Security

Encoder Security Servers shall allow Method invocation only for Sessions using user accounts with the right to invoke the Encoder Methods . There shall exist user accounts with restricted rights (that
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>

11.1 Conformance Units

Server PNENC Security Roles Server supports role-based security and restricts Method invocation to Sessions with granted "Operator" role. This includes support of the OPC UA "Security
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model

6.11 Security

Security Servers shall allow the invocation of the SetApplicationTag Method only for Sessions of user accounts to which the right for Method invocation is explicitly granted. There shall exist user
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

6.2 PROFINET Drive Security

PROFINET Drive Security Servers shall allow Method invocation only for Sessions using user accounts with the right to invoke Methods . There shall exist user accounts with restricted rights (that
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives

10.1 Conformance Units

Server PDRV Security Roles Server supports role-based security and restricts Method invocation to Sessions with granted "Operator" role. This includes support of the OPC UA "Security
OPC-30300 – Using Generic Trust Anchor (GTA) API with OPC UA - Part 1: Generic Trust Anchor (GTA) API Profile for OPC UA

5.6 CreateSession and ActivateSession

CreateSession and ActivateSession CreateSession and ActivateSession are used to establish Sessions based on the UserIdentity . CreateSession and ActivateSession can be supported by the following TrustAnchor capabilities: Computation of asymmetric cryptographic
OPC-30400-1 – OPC UA for Cloud Library - Part 1: Overall Architecture and Use Cases

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-30500-1 – OPC UA for Laboratory & Analytical Device Standard (LADS) - Part 1: Basics

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri 's location in the table has changed
OPC-34100 – OPC UA for Energy Consumption Management

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40020-1 – OPC UA for Cranes and Hoists - Part 1: Base Model Motion Devices System

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40083 – OPC UA for Plastics and Rubber Machinery - General Type Definitions

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40100-2 – OPC UA for Machine Vision - Part 2: Asset Management and Condition Monitoring

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40210 – OPC UA for Geometric Measurement Systems

5.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40223 – OPC UA for Pumps and Vacuum Pumps

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40250-1 – OPC UA for Compressed Air Systems - Part 1: Main Control Systems

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40301 – OPC UA for Flat Glass Processing

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40400-1 – OPC UA for the Powertrain - Part 1: Asset Management

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40444 – OPC UA for Textile Testing Devices

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base

4.3.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40503-1 – OPC UA for Metal Forming - Part 1: General

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40504-1 – OPC UA for Cutting Tools - Part 1: Manufacturing

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40505 – OPC UA for Wireless Machine Tool Peripherals

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40530 – OPC UA for Laser Systems

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40540 – OPC UA for Additive Manufacturing

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical Interface

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40560 – OPC UA for Mining - General

4.3.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40570 – OPC UA for Wire Harness Manufacturing

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri 's location in the table has changed
OPC-40600 – OPC UA for Weihenstephan Standards

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40700 – OPC UA for Surface Technology - General Types

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40702 – OPC UA for Surface Technology - Organic Coating Technology - Material Supply Systems

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40718 – OPC UA for Surface Technology - Shot Blasting Machinery

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40719 – OPC UA for Plasma Surface Technology

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed
OPC-40740 – OPC UA for Process Air Extraction and Filtration Systems (PAEFS)

4.2.3.2 Namespaces

Client and an OPC UA Server - the NamespaceIndex can change between Sessions and still identify the same item even though the NamespaceUri's location in the table has changed