Search

30 result(s) for PullManagement

• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  3.1.19 PullManagement
  PullManagement a workflow where a Client manages its configuration by using a GlobalService. Note 1 to entry: the Client may be an administrative tool to manage configuration for other applications
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.3 Client connections to global services
  short maximum session timeout on the GDS. Actions performed cyclically by applications during PullManagement shall start the second cycle with a random delay that is between one and at least
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.4 Application Registration Workflow
  following options are possible to complete the registration with the CertificateManager : Continue with PullManagement using the existing connection to the GDS. This option is typically used by Clients executing ... registration in an interactive mode for their own identity. See 7.6 for the PullManagement workflow. Continue with PullManagement inside a headless application. Continue with PushManagement . Set application Certificate
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.1 Overview
  described in OPC 10000-2 . There are two primary models for Certificate management: PullManagement and PushManagement . In PullManagement , the application acts as a Client and uses the Methods ... CertificateManager but a CertificateManager shall provide an integrated system that includes both push and PullManagement
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.3 Pull Management
  Pull Management PullManagement is performed by using the CertificateManager information model, in particular the Methods defined in 7.9 . The interactions between application and CertificateManager during PullManagement are illustrated in Figure ... similar process is used to renew certificates or to periodically update TrustList . Security in PullManagement requires an encrypted channel and authorized credentials. These credentials may be user credentials
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.5 Application Setup
  available and managing Certificates . Applications using a Client interface can be setup using the PullManagement . Applications using a Server interface can be setup using the PushManagement . PushManagement and PullManagement ... Device is authenticated the Device is trusted and can use the push or PullManagement without additional administrator credentials. OPC UA Servers that do not support OPC 10000-21 typically auto
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.6 Pull Management Workflow
  during registration). The UserTokenType is always Anonymous using the ApplicationSelfAdmin Privilege . The workflow for PullManagement is shown in Figure 15 and the steps are described in Table ... Figure 16 - The Pull Management Options for Key Pair Creation The steps of the PullManagement workflow are described in detail in Table 21 . Table 21 - Certificate Pull Management Workflow Steps
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.1 TrustListType
  ways. The LastUpdateTime of a TrustList Object in a CertificateManager allows Clients using the PullManagement to know whether the TrustList has changed since the last time they accessed
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.3 OpenWithMasks
  band changes it shall ensure the Client receives a consistent snapshot. For PullManagement , this Method shall be called from an authenticated SecureChannel and from a Client that has access
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.5 CloseAndUpdate
  then the associated field is not changed. For PullManagement , this Method shall be called from an authenticated SecureChannel and from a Client that has access to the CertificateAuthorityAdmin Role
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.6 AddCertificate
  This Method returns Bad_NotWritable if the TrustList Object is read only. For PullManagement , this Method shall be called from an authenticated SecureChannel and from a Client that has access
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.7 RemoveCertificate
  This Method returns Bad_NotWritable if the TrustList Object is read only. For PullManagement , this Method shall be called from an authenticated SecureChannel and from a Session that has access
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.3.2 GetRejectedList
  this list that have no unsuppressed validation errors but are not trusted. For PullManagement , this Method is not present on the CertificateGroup . For PushManagement , this Method shall be called from
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.1 Overview
  single application. There are two primary models for KeyCredential management: pull and PushManagement . In PullManagement , the application acts as a Client and uses the Methods on the KeyCredentialService to request
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.3 Pull Management
  supported by the KeyCredentialService . The interactions between the Client and the KeyCredentialService during PullManagement are illustrated in Figure 25 . Figure 25 - The Pull Model for KeyCredential Management The Application Administration ... shall only be returned to applications which are authorized by the KeyCredentialService . Security in PullManagement requires an encrypted channel and Clients with access to the KeyCredentialAdmin Role, the ApplicationAdmin Priviledge
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  8.5.1 Overview
  Overview The AddressSpace used for PullManagement is shown in Figure 27 . Clients interact with the Nodes defined in this model when they request or revoke KeyCredentials for themselves
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  G.1 Application Setup with PullManagement
  Application Setup with PullManagement Applications that use PullManagement (see 7.3 ) to setup their configuration shall know the location of the CertificateManager which they can use to request Certificates and download
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.6 DCA Client
  Client a DCA which is a Client and supports PullManagement
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.9 Device Configuration Application (DCA)
  same Device . Note 1 to entry: a DCA which is a Client uses PullManagement (see 7.2 ) to interact with the Registrar. Note 2 to entry: the Registrar uses PushManagement
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.2.4 Trust on First Use (TOFU)
  will either attempt to discover a network service that it can get its configuration ( PullManagement , see 7.2 ) or wait for another application to provide its configuration ( PushManagement , see 7.3 ). Once
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.3.2 Onboarding
  Device Configuration Application (DCA) which interacts with the Registrar using the interactions described in PullManagement ( 7.2 ) or PushManagement ( 7.3 ). These interactions are secured with a DeviceIdentity Certificate . After authentication completes
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.3.5 Operation
  update the TrustList and/or renew the Application Instance Certificate using the CertificateManager PushManagement or PullManagement described in OPC 10000-12 . Some Devices may allow the Application configuration to be changed
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.3 Authentication
  depending on whether it is a Client or a Server . Clients use PullManagement which is defined in 7.2 . Servers use PushManagement which is described in 7.3 . Devices which
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  7.1 Overview
  Applications running on the Device. This Certificate is called the DCA Certificate . When using PullManagement ( 7.2 ) the DCA connects to the Registrar without security and calls the ProvideIdentities Method
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.1 Overview
  Clause 9.2 defines the Information Model implemented in a Registrar that provides support for PullManagement defined in 7.2 . Clause 9.3 defines the Information Model implemented in a DCA Server that
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.2.2 DeviceRegistrarType
  Mandatory 0:HasComponent Object 2:Administration 2:DeviceRegistrarAdminType Optional Conformance Units Onboarding Registrar PullManagement The ProvideIdentities Method allows a Device to request that it be authenticated so it can have ... expectation is calling this Method would start a background task register the Device using PullManagement . If an administration Client needs to register many Devices it can call the RegisterDeviceEndpoint Method
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.2.3 ProvideIdentities
  have access to the network. It is called by a Device using PullManagement to provide the Registrar with its DeviceIdentity Certificates . The Registrar follows the process described
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.3.1 Overview
  location of the Registrars to be manually provided if the Device needs to use PullManagement and no multicast discovery capabilities are available. Figure 11 - Device Address Space for Onboarding Workflows
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.3.3 ProvisionableDeviceType
  more Registrars which the Device can use to authenticate itself via PullManagement . The :<ApplicationName> Objects defines an API which represents the configuration of an Client or Server running
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.3.5 SetRegistrarEndpoints
  more Registrars which the Device can use to authenticate itself via PullManagement . The Client may be an engineering tool or other administrative application that allows a human to provide information ... registrars ); Argument Description registrars The Servers which allow a Device to be authenticated via PullManagement . Method Result Codes (defined in Call Service) Result Code Description Bad_UserAccessDenied The Session does