Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ PI Server Installation and Configuration (PI Server 2024 R2)

Configure SDK authentication protocols

  • Last UpdatedOct 02, 2024
  • 1 minute read

When an SDK application tries to connect to the PI Server, it tries all available authentication methods until it succeeds. You can configure the order in which it tries the authentication methods. The possible methods are:

  • Windows Security. If a valid PI mapping exists for the Windows user (or for any group to which the user belongs) then the user is authenticated as the PI identity, PI user, or PI group defined for that mapping.

  • PI Trust. If the connection request matches an existing PI trust, then the user is authenticated as the PI identity, PI user, or PI group defined for that trust.

  • Default User. A default PI user account.

The first method that succeeds defines the access permissions granted to the connecting application. Once one authentication method succeeds, no other methods are tried. By default the SDK (1.3.6 and later) tries to authenticate first through Windows.

You can configure which methods the SDK tries first.

  1. Using the PI SDK utility, select File > Connections.

  2. Select the PI Server and then select Connections > Options.

  3. Under Specify Authentication Procedure, select the protocols to support and move them from the Available protocols list to the Protocol order list. Then, use the Protocol order list to arrange the order in which protocols should be tried.

TitleResults for “How to create a CRG?”Also Available in