Search

16 result(s) for ANONYMOUS

• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.7.1 Description
  that the Client of that Session is operating on behalf of the same non- ANONYMOUS ClientUserId . The ClientUserId is defined in OPC 10000-5 . If the Client uses an ANONYMOUS
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  6.7 Re-establishing connections
  Session . Transfer subscription shall be accepted by a Server even for Anonymous user if the Client does not change i.e. the ApplicationUri of the Client does not change
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.5 X509IdentityTokens
  configurable time after the token expires. The Session shall stay valid with the Anonymous Role . If the Server does not allow anonymous users, it should close the Session . Clients should
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.40.6 IssuedIdentityToken
  configurable time after the token expires. The Session shall stay valid with the Anonymous Role . If the Server does not allow anonymous users, it should close the Session . Clients should
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.41 UserTokenPolicy
  user identity token required. The UserTokenType is defined in 7.42 A tokenType of ANONYMOUS indicates that the Server does not require any user identification. In this case, the Client ApplicationInstanceCertificate
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.3 UANode
  Roles specified, however, they may not make the Node more accessible. For example, Anonymous or AuthenticatedUser Roles shall not be granted more access to the Node than is specified
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.6 Pull Management Workflow
  signed by the CertificateManager (or the Certificate assigned during registration). The UserTokenType is always Anonymous using the ApplicationSelfAdmin Privilege . The workflow for PullManagement is shown in Figure ... CreateSession and ActivateSession are used to create a connection with MessageSecurityMode SignAndEncrypt and an Anonymous user. The default CertificateGroup from the Client configuration is used to establish the connection. Application
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.25 UserTokenSettingsDataType
  verify the Signature on an IssuedIdentityToken . The CertificateGroup is not specified for UserName or Anonymous TokenTypes . The KeyCredentialName is only specified for IssuedIdentityTokens and refers to a KeyCredential needed
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  G.2 Application setup with the PushManagement
  determine that the Server is in the Application Setup state by reconnecting using Anonymous user credentials and checking the ServerState Property . Once an application has been configured it automatically leaves ... Always allow Clients to connect securely and assign the SecurityAdmin Role to Anonymous user if the TrustList is empty; Connect to the Server after toggling a physical switch
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.12.3 PubSubKeyPushTargetDataType
  toke to be used for the connection to the push target. The default is Anonymous . RequestedKeyCount UInt16 The number of keys that are to be pushed on each update
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.6.1 PubSubKeyPushTargetType definition
  user toke to be used for the connection to the PubSubKeyPushTarget . The default is Anonymous and authorization is accomplished in this case with the application identity
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.7.2 AddPushTarget Method
  PushTarget UserTokenType The user token type used for the push. The default is Anonymous . RequestedKeyCount The number of keys to push on each call RetryInterval Interval the SKS shall
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.3 RoleSet
  ComponentOf the ServerCapabilities Object defined in OPC 10000-5 HasTypeDefinition ObjectType RoleSetType HasComponent Object Anonymous RoleType HasComponent Object AuthenticatedUser RoleType HasComponent Object TrustedApplication RoleType HasComponent Object Observer RoleType HasComponent Object ... known Roles which are defined in OPC 10000-3 . The default Identities for the Anonymous Role shall be Identities with the criteriaType IdentityCriteriaType.Anonymous and the criteriaType IdentityCriteriaType.AuthenticatedUser . The Anonymous Role
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.4.3 IdentityMappingRuleType
  depends on the criteriaType . The criteria shall be null or an empty string for Anonymous, AuthenticatedUser and TrustedApplication . If the criteriaType is UserName , the criteria is a name ... value of "iss" followed by a '/' (slash). If the criteriaType is Anonymous , the criteria shall be null or an empty string. The criteriaType applies if no user credentials
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  4.4.4 IdentityCriteriaType
  Token . GroupId 4 The rule is a user group specified in the Access Token. Anonymous 5 The rule specifies Anonymous UserIdentityToken. AuthenticatedUser 6 The rule specifies any non Anonymous UserIdentityToken
• OPC-10000-18 – OPC Unified Architecture - Part 18: Role-Based Security
  5.2.8 ChangePassword Method
  ActivateSession shall return Good_PasswordChangeRequired and the activated Session shall have only the Role Anonymous . In this state, the Session shall be allowed to call ChangePassword for the user that ... type for the Session is USERNAME, even if the Role for the user is Anonymous . Signature ChangePassword ( [in] String OldPassword, [in] String NewPassword ); Argument Description OldPassword The old password