Configure PI interface connections using PI trusts

PI trusts are still available as a method for authenticating PI interfaces. However, the use of PI trusts for interfaces should be reserved to cases where Windows authentication cannot be used. For example, the interface node is running an older version of the PI API and cannot be upgraded at this time. Instead, use the PI API 1.6.8 or earlier and configure this connection using PI trusts for authentication.

Note: If the client application does not support Windows authentication and/or must connect to PI Server versions prior to 3.4.380, do not install or upgrade to PI API 2016 for Windows Integrated Security, as it does not support PI trusts or explicit logins.

Configure your Data Archive server to provide access for PI interfaces using PI trusts on PI API 1.6.8 or earlier.

1. Identify all the PI interfaces that need access to the Data Archive server.

2. Consult the documentation for each interface and gather the information you need to configure the PI trust. You need to know the connection type (Learn about connection types for PI API and PI SDK). The type of connection determines what information you can use to define the trust. You will also need to specify at least one of the following:

   • The correct application name to use when defining the trust (Learn about the application name)

   • IP information for the connecting computer (IP information in SMT)

   • For SDK connections only, you have the option to specify Windows account information, but this is not recommended (Windows account information)

3. Decide how many PI trusts you will create.

   You can create explicit individual trusts for each PI interface or you can group them according to subnet, host machine, or username. A group of PI interfaces can share the same privileges.

4. For each PI trust, create a PI identity.

   See Create a PI identity.

5. Give that PI identity all the access permissions required by the PI trust.

   See Learn about product access permissions and configuration issues as well as the documentation for the interface.

6. Create a trust based on that PI identity.

   See Create a trust.