choose PI API Version during installation
At the moment PI API 1.x without Windows Integrated Security is installed as standard. For customers who want to use PI API 2.x with Windows Integrated Security an additional installation is needed. please include both APIs in install-pack and ask during installation what Version should be installed.
FranzK
shared this idea
We pride ourselves on making security a high priority, and PI API for Windows integrated security (WIS) is a prime example of that in product form. However, the first rule of cyber security is to do no harm. We do not package PI API for WIS with interfaces because it requires security configuration changes that cannot be handled by the interface installer. As opposed to failing the installation, we have decided to continue to package PI API 1 with PI Interfaces and make PI API for WIS available as a standalone download. This will allow you to carry out the manual steps needed to leverage Windows Integrated Security for PI Interfaces.
2 comments
-
Kenneth Barber
commented
I don't understand why the PI API version even downgrades at all. If a higher version of anything is installed, it usually remains untouched, but not with PI API.
-
James Jones
commented
In my opinion, the installer should automatically detect which PI API version is installed and adjust accordingly (like it does in setup initialization for all other modules when it decides what will be installed, upgraded or not upgraded).
I lost a lot of time troubleshooting when upgrading ModbusE interface which was configured using PI API was downgraded to version1.6 because it was looking for trusts when it was previously connecting using WIS.