PI Data Archive authentication and buffering
- Last UpdatedJan 13, 2023
- 1 minute read
Configure a PI mapping or PI trust for both PI Buffer Subsystem and the buffered application so they can authenticate with Data Archive using the specified PI identity, PI user, or PI group. The recommended authentication method varies depending on the Data Archive version and the application connecting to the server.
|
Data Archive version |
Application connecting to Data Archive |
Recommended authentication method |
|---|---|---|
|
3.4.375 |
PI Buffer Subsystem |
PI trust; this version of PI Data Archive does not support Windows authentication |
|
Buffered application (PI API or PI SDK) |
PI trust; this version of PI Data Archive does not support Windows authentication |
|
|
3.4.380 or later with PI API 1.6.8 or earlier |
PI Buffer Subsystem |
Windows authentication (PI mapping) |
|
Buffered PI client or other AF SDK or PI SDK application |
Windows authentication (PI mapping) |
|
|
Buffered PI interface or other PI API application |
PI trust; connections using these versions of PI API do not support Windows authentication |
|
|
2016 R2 (3.4.405) or later with PI API 2016 for Windows Integrated Security |
PI Buffer Subsystem |
Windows authentication (PI mapping) |
|
Buffered application (PI API or PI SDK) |
Windows authentication (PI mapping) |
Note: If a DNS provides both forward and reverse name lookups, define PI Trusts using fully-qualified domain names (FQDN). In other cases, IP addresses are accepted. In all cases, restrict the trust by specifying the Appname (application name), such as pibufss.exe.