Search
10 result(s) for KeyCredentialService
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services3.1.12 KeyCredentialServiceKeyCredentialService a software application that provides KeyCredentials needed to access an AuthorizationService or a Broker
-
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model8.1 OverviewServices for a plant or entire system. In addition, This Server can include CertificateManager , KeyCredentialService and AuthorizationService (defined in OPC 10000-12 ). There are multiple methods of accessing
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Servicesalso be a CertificateManager . Note 2 to entry: a GDS may also be a KeyCredentialService . Note 3 to entry: a GDS may also be a AuthorizationService
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services3.1.9 GlobalServiceCapabilities needed for a system. Note 1 to entry: a GlobalDiscoveryServer , a CertificateManager , a KeyCredentialService and an AuthorizationService are all examples of GlobalServices
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services8.1 OverviewAuthorizationServices and/or Brokers . An application that provides the KeyCredential management functions is called a KeyCredentialService and is typically combined with the GDS into a single application. There are two primary ... PullManagement , the application acts as a Client and uses the Methods on the KeyCredentialService to request and update KeyCredentials . The application is responsible for ensuring the KeyCredentials are kept
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Servicesmechanisms other than the well-known Roles . The well-known Roles used for a KeyCredentialService are listed in Table 120 . Table 120 - Well-known Roles for a KeyCredentialService Name Description ... KeyCredential . SecurityAdmin This Role grants the right to change the security configuration of a KeyCredentialService. The well-known Roles for Server managed by a KeyCredentialService are listed in Table
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services8.3 Pull Managementallows Clients to request credentials for AuthorizationServices or Brokers which are supported by the KeyCredentialService . The interactions between the Client and the KeyCredentialService during PullManagement are illustrated in Figure ... button. KeyCredentials 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
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services8.4 Push ManagementServerConfiguration Object in a Server . The interactions between the Administration application and the KeyCredentialService during PushManagement are illustrated in Figure 26 . Figure 26 - The Push Model for KeyCredential Management ... built and are not a requirement. To ensure security of the KeyCredentials, the KeyCredentialService component can require that secrets be encrypted with a key only known to the intended recipient
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services8.5.4 KeyCredentialServiceTypeResourceUri Property uniquely identifies the resource that accepts the KeyCredentials provided by the KeyCredentialService Object . The ProfileUris Property specifies URIs assigned in OPC 10000-7 to the authentication mechanism used
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services8.5.6 FinishRequestused. The Signing Certificate is owned by the source of the KeyCredential. The KeyCredentialService determines the most appropriate Certificate to use. If the return code is Bad_RequestNotComplete then ... again. It is expected that a Client will periodically call this Method until the KeyCredentialService has completed the request. This Method shall be called from an encrypted SecureChannel and from