How will PI API 2016 for Windows Integrated Security affect clients and interfaces?

Windows Integrated Security is the recommended security model for Data Archive server and clients, including PI interfaces. All PI Server 3.4.380 or later support Windows Integrated Security for the server side. For PI API-based client applications, extending this security model involves upgrading to PI API 2016 for Windows Integrated Security.

• When should I upgrade to PI API 2016 for Windows Integrated Security?

  You should upgrade if your client supports Windows authentication.

• When should I not upgrade my PI API?

  You should defer PI API 2016 upgrade if your Windows platform is unable to meet minimum requirements or if you need more time to verify compatibility with a custom PI API application.

• What are the requirements to upgrade to PI API 2016 for Windows Integrated Security?

  The account that is running the API must be able to generate a Windows login context that can authenticate with the Data Archive computer. Note the computer running the API application does not need to be a member of a domain. Separate credentials can be stored in Windows Credential manager to authenticate with the Data Archivecomputer when the API is running on a workgroup computer.

• I am not upgrading my PI API. However, I want to upgrade my Data Archive to 3.4.395. Will upgrading my Data Archive server affect my existing PI trusts?

  There is no effect on your existing PI trusts, and they authenticate as normal. If, additionally, you upgrade to PI API 2016 for Windows Integrated Security, then your existing PI trusts will not work as expected. This is because PI trusts are not supported once PI API is upgraded to PI API 2016 for Windows Integrated Security.