Security

Currently, when you create a mapping in PI Data archive for OIDC client credentals, you can only assign one identity.This severely limits the granularity and forces to add new identities to existing tags to grant extra permissions and is an easy s...

Currently, AIM can only use CONNECT or Microsoft Entra ID as the main Identity Provider. Configuring any other IDP requires federation through CONNECT. Allowing other IDPs to work directly with AIM without CONNECT would simplify the OIDC configura...

Read access to the PIPOINT table is required for most identities. Pointsecurity and Datasecurity currently use the settings on the PIPOINT table as the default. New points will generally give read access to most identities because of these default...

PI SMT should be able to authenticate users by using OIDC.

Possibility to identify in SMT which connections are OIDC, besides the "Is TLS" in Network Manager Statistics.

AVEVA Identity Manager app (PCS) should have option to select a custom DNS Alias name through the UI.

Currently the maximum password length for AF Linked Table connections using the "Supply Password" option is 15 characters. This length limitation should be increased to at least 25 characters.

We have some user that are able to edit some fields in AF using System explorer but they cannot do it using PI Builder (that require database access). Please align PI Builder access and PI System explorer because the actual situation is a nonsense

Instead of having several admlin tools to manage the security for data archive, AF, PI Vision, PI Integrators Could you provide a centralized security management interface which could manage all the existing and upcoming OSIsoft tools

As a PI System administrator, I need to harden the OS of my servers consistent with industry best practices so that they are resilient to attack and random disruption. Official testing of compatibility with industry standards such as the Windows ...