Security

I want to run the Auditviewer function as a unprivileged remote user, moving away from the current requirement to run as a local user on the PI Data Archive Server.  This is so I can minimize security risk associated with local user access on...

Currently, there are 2 windows to configure PI AF security, and it is a pain to switch between them: File → Database → Edit Security, which is used to assign permissions to identities File → Server Properties → Identities tab and Mappings tab, whi...

Use case: We want to give a user read access to a single element. All future elements created inherit the Database level Security, meaning the user will also have read access to all future created elements.

Implement a way to hide the contents of a PI point attribute, specifically the Instrumenttag attribute. With many PI interfaces, the InstrumentTag attribute will store the IP address of the source, and we (as well as many other utilities) have a r...

In PI System Explorer, the definitions of the Read, Write, Read Data, and Write Data permissions are not clear from their names. Their names are also misleading. For example, Read permission can be interpreted as "General Read", making Read appear...

There should be some type of sorting feature for the Security Identities/Securities listed in the Database Security section of System Management Tools. A simple fix would be to allow us to remove an identity, re-add it and have that appear on the ...

When creating a trust for the Buffer Subsystem with the Add Data Server Wizard in Buffering Manager, the Wizard auto-populates the IP Address of the machine. Include an option to edit the IP Address that is auto-populated for machines that have mu...

The idea would be to provide a feature which alllows a PI System Admin to get a report of all the rights that are granted to a user or a group of user for all the PI system product which have a link with security

As an ICS systems engineer, I need to understand and easily configure Authentication and Authorization settings to secure the PI System from the point of data collection to data access and remote display viewing.

I want to give access to only some attributes on some elements to some users. Currently, the smallest granularity in AF Security is at the element, not attribute level. Sure there are some workarounds like creating derived templates, but it would ...