Understand how to configure PI interface connections using PI mappings
- Last UpdatedFeb 12, 2025
- 1 minute read
Starting with the release of PI API 2018 Patch 2 for Windows Integrated Security, Windows authentication and transport security extends to all client PI API-based applications, such as PI interfaces. As a result, we recommend upgrading your authentication model to Windows authentication for all applications using PI API to connect to Data Archive.
Before upgrading your PI API to PI API 2018 Patch 2 for Windows Integrated Security, you must perform the preparatory process outlined in the following sections.
Caution: PI API 2018 Patch 2 does not support PI trusts and explicit logins. Before upgrading your PI API to PI API 2018 Patch 2 for Windows Integrated Security, you must first configure PI mappings to replace any existing PI trusts or explicit logins on PI API. In order to configure a PI mapping, you will need a Windows logon or service account for the PI API application.
Related Links
- Task 1: Ensure system requirements
- Task 2: Identify all PI trusts and corresponding PI identities
- Task 3: Identify Windows account for your interfaces
- Task 4: Change the login credentials for your interfaces
- Task 5: Create PI mappings between the Windows account and PI identities
- Task 6: Retire PI trusts